survey-design
Skill1 starsChanged 38 days agoMITView on GitHub
Design a survey with unbiased questions, the right scales, a sensible length and an analysis plan, and review existing surveys for bias. Use when someone wants to write a survey, questionnaire, NPS or satisfaction survey, or wants to know how many responses they need.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- teodstr/garagetheir own version, first seen Nov 15, 2026
- henrique-simoes/Istaratheir own version, first seen Sep 27, 2026
- stritar/skillstheir own version, first seen Sep 11, 2026
- unbias38/my-claude-skillstheir own version, first seen Jul 6, 2026
- miovrag/claude-skillstheir own version, first seen Jun 12, 2026
- Xipher-Labs/walter-ostheir own version, first seen May 21, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- xjtulyc/awesome-rosetta-skills★ 34same name
- henrique-simoes/Istara★ 15same name
- Xipher-Labs/walter-os★ 8same name
- unbias38/my-claude-skills★ 2same name
- miovrag/claude-skills★ 1same name
- nandanosql/all_in_one_pm_skills★ 1same name
- stritar/skills★ 0same name
- teodstr/garage★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- accessibility-researchSkill
- ai-browser-walkthroughSkill
- analytics-insightsSkill
- card-sort-tree-testSkill
- competitive-analysisSkill
- diary-studySkill
- interview-guideSkill
- jobs-to-be-doneSkill
- journey-mapSkill
- research-planSkill
- research-readoutSkill
- screener-surveySkill
- stakeholder-interviewsSkill
- synthetic-usersSkill
- usability-test-analysisSkill
- usability-test-planSkill
- user-personasSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Start from what you'll do with the answers: Every question maps to a decision or an analysis.
- Distinctive: line 27
Don't ask people to predict their future behaviour and treat it as a forecast.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Survey design
Surveys count things. Use them when you need to know how many, not why.
Steps
- Start from what you'll do with the answers. Every question maps to a decision or an analysis. Cut the rest.
- Ask about behaviour and facts first, opinions second. "How many times did you compare quotes last year?" before "How satisfied are you?"
- Write neutral questions: one idea per question, no leading words, no double negatives, balanced scales with a neutral point and a "not applicable" when needed.
- Order: easy and relevant first, sensitive and demographic last, demographics optional.
- Length: under ten minutes. Long surveys get rushed answers.
- Sample: say who it's going to, how they're reached, and who's missing (people who already left, people who don't open email). For estimating a percentage, a few hundred responses gives a usefully narrow range; explain the margin rather than overselling precision.
- Pilot with five people and fix what confused them.
- Privacy: collect only what you need, say how it's used, keep answers anonymous where possible.
Output
The survey with question types and answer options, the reason for each question, the analysis plan, and the sampling notes.
Don't
- Don't ask people to predict their future behaviour and treat it as a forecast. Don't make every question required.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

