to-questionnaire
- Use it when:
- A decision hinges on knowledge someone else has, and you need to get it out of them.
- It does:
- Asks you who the recipient is and what you need back, then writes the questions for them.
- You get:
- A Markdown questionnaire in the current folder, to send for written answers or to fill in together in a meeting.
- Unlike grilling:
- That skill questions you about your own plan; this one asks you only about the recipient and what you need.
- Runs:
- Only when you invoke it; the agent won't start it on its own.
TL;DR
It doesn't question you about the subject, since that's the part you can't answer. It asks two things, each in one go: who the questionnaire is for (their role, what they know, how they relate to you) and which decisions or facts you need back from them. The questions then aim at the gap between the two. It writes to-questionnaire-<topic>.md: the purpose and the decision riding on it, who it's from and to and how the answers will be used, one paragraph of context, a deadline and a note that "I don't know" is a useful answer, then the questions grouped by theme. They come most important first, since a written reply may come only once. Each asks one thing, leaves room for the answer right below, and adds a one-line "why this matters" where it could be misread. It ends with an "anything else?" catch-all, and the agent checks that everything you said you need is covered.
Summarizes the skill at 5beb35b.
npx skills add https://github.com/mattpocock/skills --skill to-questionnaire skills.sh pageSource on GitHubAll skills from mattpocock/skills
More weekly downloads than 97% of skills
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 35,563 |
| Sep 28 | 31,444 |
| Oct 5 | 31,576 |
| Oct 12 | 40,802 |
| Oct 19 | 34,949 |
| Oct 26 | 30,800 |
| Nov 2 | 28,664 |
| Nov 9 | 27,431 |
More downloads than 97% of skills
More stars than 98% of repos
Newer than 89% of skills
| Category |
Make the agent question you and write the plan down before it writes code. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A one-shot action you invoke by name, such as turning the conversation into a PRD. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From mattpocock/skills at 5beb35b. Checked daily, last changed Oct 20, 2026.
Frontmatter
name: to-questionnaire
description: Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
disable-model-invocation: trueTurn something the user can't answer alone into a questionnaire: a Markdown document they hand to one person to fill in async, or fill out together over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.
Grill the send, not the subject. Interview the user only about the send, which they can always answer: who it goes to, and what they need back. The questions in the document then target the gap between what the recipient knows and what the user needs.
-
Who is it going to? Ask, in one exchange, the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user doesn't.
-
What do you need back? Ask, in one exchange, the specific decisions or facts the user can't resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide.
-
Write the questionnaire. Draft questions aimed at the gap from steps 1–2, following the Document structure below. Write it to
to-questionnaire-<slug>.mdin the current directory (slug from the topic) and report the path. Done when the file exists and every item the user named in step 2 is covered by a question.
Document structure
Frame the document as a discovery questionnaire: the user lacks context, the recipient holds it. Order questions most-important-first, since async means you may only get one pass, and group them under ## headings by theme once there are more than a handful. Write it using the template below.
<questionnaire-template>
<Questionnaire title>
Purpose: why this questionnaire exists and the decision riding on it.
From: <the user>, To: <the recipient>, How your answers will be used: <where they go>
Context
One paragraph orienting a recipient who wasn't in the user's head. Enough to answer well, not a page.
How to answer
Deadline and rough effort. Partial answers and "I don't know" are useful: flag anything you're unsure of rather than skipping it.
<Theme heading>
One ## section per theme. Under each, its questions, most-important-first. Every question is one idea, never compound, with an answer stub directly beneath, and a one-line why this matters only where the question could be misread or invite a throwaway answer.
<question-example>
What load is the system expected to handle at launch?
Why this matters: it decides whether we provision for burst traffic now or defer it.
</question-example>
Anything else?
A closing catch-all: anything we didn't ask that we should know?
</questionnaire-template>