survey-design
Skill0 starsChanged 2 days agoMITView on GitHub
Design a survey that measures something useful without biasing the answers: one decision to inform, the right sample, neutral questions, balanced scales, a pilot, and an honest analysis with margins of error. Use for market research questionnaires, customer satisfaction, pricing or feature preference surveys. Triggers: "survey", "questionnaire", "poll", "Likert", "sondage", "questionnaire en ligne", "étude quantitative", "enquête", "encuesta", "cuestionario", "estudio cuantitativo".
8 other projects use a version of this.
Adopted by
Most recently taken up by
- miguelclavel/ux-research-skillstheir own version, first seen Nov 8, 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
- miguelclavel/ux-research-skills★ 1same name
- miovrag/claude-skills★ 1same name
- nandanosql/all_in_one_pm_skills★ 1same name
- stritar/skills★ 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 repository15 other files it gives its agents.
- brand-identitySkill
- competitor-teardownSkill
- customer-interviewsSkill
- desk-researchSkill
- financial-forecastSkill
- first-customersSkill
- funding-optionsSkill
- idea-validationSkill
- landing-pageSkill
- legal-setupSkill
- mvp-scopingSkill
- pitch-deckSkill
- prototype-testingSkill
- startup-roadmapSkill
- support-programsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
After customer-interviews, to measure how common a problem, a habit or a preference is.
- Distinctive: line 21
Not to discover new problems, and not to forecast sales: "would you buy it?" answers overstate real demand.
- Distinctive: line 31
One decision, a few numbers: write the decision and the three to five numbers needed to make it.
- Distinctive: line 58
Every question maps to the decision.
“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
A survey can only measure what interviews have already uncovered, and a badly written one measures the questionnaire instead of the market. This skill builds short, neutral surveys and reads the results with the right caution.
When to use
- After
customer-interviews, to measure how common a problem, a habit or a preference is. - To compare segments or track satisfaction over time.
- Not to discover new problems, and not to forecast sales: "would you buy it?" answers overstate real demand.
Inputs
- The decision the survey informs.
- The target population and how to reach it.
- Constraints: budget, deadline, survey tool.
Method
- One decision, a few numbers: write the decision and the three to five numbers needed to make it. Every question feeds one of them; cut the rest.
- Define the population and the sample: who exactly, how they will be reached, and the bias of that channel (a post on the founder's social network reaches the founder's network, not the market).
- Compute the margin of error for a proportion, and say that it only holds for a random sample: margin = 1.96 × √(p × (1 − p) / n). With p = 0.5, it is about ±9.8 points for 100 answers and ±4.9 points for 400.
- Write neutral questions: one idea per question, no loaded words, no jargon, a "don't know" or "not applicable" option when it fits, balanced scales (as many positive as negative points), a precise time frame ("in the last 30 days").
- Order the questionnaire: screening questions first, easy factual questions next, sensitive ones (income, age) last. Keep it under ten minutes and shuffle answer options when their order could matter.
- Ask about behavior when possible: "What did you use last time?" beats "What would you use?". Treat purchase intent as an upper limit, never as a forecast.
- Pilot it with five people from the target who think aloud while answering, then fix what confused them.
- Analyze honestly: report the number of answers, the response rate, the sample's bias and the margins of error; compare segments only when each has enough answers; show the exact wording next to each result.
Output
### Survey plan
Decision: … | Numbers needed: … | Population: … | Channel and its bias: …
Planned sample: n = … (margin of error ±… points, random sample only)
### Questionnaire
| # | Question (exact wording) | Type and scale | Feeds which number |
|---|---|---|---|
### Results
| Number | Result | n | Margin of error | Caveat |
|---|---|---|---|---|Quality bar
- Every question maps to the decision; none is leading, double or hypothetical without a warning.
- Margins of error are computed, not guessed, and the sampling bias is stated.
- Purchase-intent answers are never presented as a sales forecast.
- The survey says how answers will be used, and personal data is kept to a minimum (GDPR in the European Union).
- Written in the user's language, with the terms below.
Terminology
| English | Français | Español |
| Survey, questionnaire | Questionnaire, enquête | Encuesta, cuestionario |
| Sample | Échantillon | Muestra |
| Margin of error | Marge d'erreur | Margen de error |
| Response rate | Taux de réponse | Tasa de respuesta |
| Leading question | Question orientée | Pregunta sesgada |
| Likert scale | Échelle de Likert | Escala de Likert |
Sources
- Dillman, D. A., Smyth, J. D., & Christian, L. M. (2014). Internet, Phone, Mail, and Mixed-Mode Surveys: The Tailored Design Method (4th ed.). Wiley.
- Saunders, M., Lewis, P., & Thornhill, A. (2019). Research Methods for Business Students (8th ed.). Pearson.
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.

