Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aivrar/decision-questionnaire
Turn an unanswerable decision into a questionnaire doc.
Passed 16 of 22 test cases with the skill, and 9 of 22 without it.
and 8 more in the full report
9 fixed8 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
If a decision questionnaire covers vendor selection for Snowflake data warehousing, what standard naming convention should be used when writing the markdown file to disk?
| Checked | Without skill | With skill |
|---|---|---|
| The file name starts with the prefix decision-questionnaire-. | Missed | Passed |
The instructions your model reads when the skill loads.
Turns 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 in a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.
Ported from mattpocock/skills' MIT-licensed to-questionnaire skill.
Do NOT use when the answer is discoverable from the environment (codebase, docs, web) — find it yourself first.
The user cannot answer the subject-matter questions (that's the point), but they can ALWAYS answer questions about the send. Interview them only about that, in two short exchanges:
Then write the questionnaire: draft questions aimed at the gap between
what the recipient knows and what the user needs, following the structure
below. Write it to decision-questionnaire-<slug>.md in the current
directory (slug from the topic) and report the absolute path. Done when the
file exists and every item from step 2 is covered by a question.
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.