Design Sprint
wondelai/skills
Run a structured 5-day process to prototype, test, and validate product ideas with real users.
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale.
Install Survey Design
$ npx skills add Owl-Listener/designer-skills --skill survey-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills survey-design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/design-research/skills/survey-design .claude/skills/survey-design && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "survey-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/survey-design into .claude/skills/survey-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "survey-design", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/survey-designType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill survey-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills survey-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/design-research/skills/survey-design .agents/skills/survey-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "survey-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/survey-design into .agents/skills/survey-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "survey-design", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill survey-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills survey-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/design-research/skills/survey-design .cursor/skills/survey-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "survey-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/survey-design into .cursor/skills/survey-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "survey-design", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path design-research/skills/survey-design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill survey-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills survey-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/design-research/skills/survey-design .gemini/skills/survey-design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "survey-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/survey-design into .gemini/skills/survey-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "survey-design", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills survey-designInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill survey-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/design-research/skills/survey-design .github/skills/survey-design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "survey-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/survey-design into .github/skills/survey-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "survey-design", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill survey-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills survey-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/design-research/skills/survey-design .opencode/skills/survey-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "survey-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/survey-design into .opencode/skills/survey-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "survey-design", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
survey-design- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~1.4k tokens
- SKILL.md length
- 719 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale.
- Works in 4 steps: Screen and demographic questions (if… → Behavioral questions (what users do) —… → Attitudinal/satisfaction questions —… → …
- You need quantitative breadth
- SKILL.md covers What You Do, When to Use Surveys, Survey Structure and Question Types, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Survey Design is an agent skill from Owl-Listener/designer-skills. Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Prototyping and A/B testing. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- You need quantitative breadth
- Tasks that involve Prototyping
- Tasks that involve A/B testing
Example prompts
- “/survey-design”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Screen and demographic questions (if needed) — short, at the start
- Behavioral questions (what users do) — before attitudinal questions
- Attitudinal/satisfaction questions — after behavioral context is established
- Open-ended questions — at the end; they require more effort and shouldn't fatigue respondents before the core questions
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Survey Design loads about 1.4k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 719 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 719 words, ~1,377 tokens.
Download SKILL.mdSave it as
.claude/skills/survey-design/SKILL.md (or your agent's skills folder).- name
- survey-design
- description
- Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use `a-b-test-design` (prototyping-testing).
Survey Design
You are an expert in designing surveys that produce reliable, actionable data — not noise.
What You Do
You design surveys with well-formed questions, appropriate scales, and sound methodology so the data you collect can be trusted and used to make decisions.
When to Use Surveys
Surveys are quantitative research: they measure prevalence, frequency, and attitude at scale. Use them when:
- You need to know how many users share a need, problem, or opinion (not just whether some do)
- You need to validate or quantify findings from qualitative research (interviews, usability tests)
- You need to measure change over time (satisfaction scores, NPS trends)
- You need a representative sample across a population segment Do not use surveys to discover problems you don't yet know exist — that's qualitative research's job. Surveys confirm and quantify; interviews explore and reveal.
Survey Structure
Introduction
- State the purpose: "We're improving [X] and want to hear your experience."
- State the time required: "This takes about 3 minutes."
- State anonymity/confidentiality if applicable
- No leading language — don't pre-frame what the "right" answers are
Question Order
- Screen and demographic questions (if needed) — short, at the start
- Behavioral questions (what users do) — before attitudinal questions
- Attitudinal/satisfaction questions — after behavioral context is established
- Open-ended questions — at the end; they require more effort and shouldn't fatigue respondents before the core questions
Closing
- Thank participants
- Provide a path to learn more or be contacted for follow-up (optional)
Question Types
| Type | Use for | Caution |
|---|---|---|
| Single-choice (radio) | Mutually exclusive options | Ensure options are exhaustive; include "Other" when needed |
| Multi-select (checkbox) | Multiple applicable answers | Don't use when you need to rank or when options are mutually exclusive |
| Likert scale | Attitudes, agreement, satisfaction | Use consistent scale direction (1=low, 5=high); always use labelled endpoints |
| Rating scale (1–10, NPS) | Single-dimension measurement | Specify what each end means |
| Ranking | Relative importance between items | Limit to 5–7 items; ranking is cognitively taxing |
| Open text | Explanation, unexpected answers | Use sparingly; qualitative responses are expensive to analyze |
Question Writing
Avoid these patterns:
- Leading questions: "How much do you enjoy using our product?" → "How would you describe your experience using our product?"
- Double-barreled questions: "How easy and enjoyable is checkout?" → Split into two questions
- Loaded language: "How satisfied are you with our fast shipping?" → Remove "fast"
- Recall overload: "In the past 12 months, how many times…" → Shorter recall periods are more accurate
- Jargon: Use the same terms users use, not internal product names
Do these instead:
- One question per question
- Specific, behaviorally grounded language
- Mutually exclusive and collectively exhaustive response options
- Neutral phrasing that doesn't suggest a preferred answer
Scales
Show full SKILL.md (290 more words)Show less
Likert Scales
- 5-point and 7-point are both defensible; 5-point is easier for respondents
- Always include a midpoint — don't force binary responses unless the question is genuinely binary
- Always label endpoints: "1 = Strongly disagree, 5 = Strongly agree"
- Be consistent with scale direction across the entire survey
Net Promoter Score (NPS)
- 0–10 scale; "How likely are you to recommend [product] to a friend or colleague?"
- Promoters: 9–10; Passives: 7–8; Detractors: 0–6; NPS = %Promoters − %Detractors
- NPS is a single, comparable metric — don't use it as a complete satisfaction measure
System Usability Scale (SUS)
- Validated 10-question scale for perceived usability
- Score 0–100 (68 is the average; above 80 is considered good)
- Use verbatim — don't modify the questions
Sampling
- Sample size: for a ±5% margin of error at 95% confidence in a large population, you need ~385 responses
- Representativeness: sample should match the demographic profile of the population you're studying
- Response bias: people who respond to surveys differ from those who don't — acknowledge this limitation
- Survey fatigue: keep surveys short (under 5 minutes); response quality drops significantly beyond 10–15 questions
Analyzing Results
- Report descriptive statistics: mean, median, distribution — not just "most people said X"
- For Likert data: show the full distribution, not just the average
- Open text: code themes; report top themes with example quotes
- Cross-tabulate by segment when segments differ meaningfully (new vs returning users, mobile vs desktop)
- Report response rate and sample size alongside every finding
Best Practices
- Pilot test with 3–5 people before sending — cognitive pretesting reveals confusing questions
- Keep surveys short; every question you add reduces completion rate and data quality
- Define your analysis plan before writing questions — "what decision will this answer?" for every question
- Pair with qualitative research: surveys tell you what and how many; interviews tell you why
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in design-research/skills/survey-design of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Survey Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Survey Design this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Design Sprintwondelai/skills | 2.4k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Loki Modedavila7/claude-code-templates | 33k | 7 repos | ~7.1k | Automated safety check: Warn | MIT | |
| Messaging Ab Testergooseworks-ai/goose-skills | 1.2k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Measure Survey Analysisproduct-on-purpose/pm-skills | 716 | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Sales Engineerborghei/Claude-Skills | 891 | — | ~4.3k | Automated safety check: Pass | MIT |
Similar skills
Loki Mode
davila7/claude-code-templates
Multi-agent autonomous startup system for Claude Code. An agent skill from davila7/claude-code-templates.
Messaging Ab Tester
gooseworks-ai/goose-skills
Generate 3-5 messaging variants for a value proposition, design structured A/B tests, and analyze results to determine which framing resonates most with ICP.
Measure Survey Analysis
product-on-purpose/pm-skills
Analyze survey results into actionable PM insights. An agent skill from product-on-purpose/pm-skills.
Sales Engineer
borghei/Claude-Skills
Analyzes RFP responses for coverage gaps, builds competitive feature matrices, and plans proof-of-concept engagements for pre-sales engineering
Sales Engineer
borghei/Claude-Skills
Technical sales engineering: demos, solution design, RFP responses, and POC management.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Questions about Survey Design
What does Survey Design do?
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Survey Design is an agent skill from Owl-Listener/designer-skills. Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale.
When should I use Survey Design?
Survey Design fits situations like: you need quantitative breadth; tasks that involve Prototyping; tasks that involve A/B testing.
How do I install Survey Design in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill survey-design -a claude-code`. Or copy the skill folder (design-research/skills/survey-design in Owl-Listener/designer-skills) into .claude/skills/survey-design in your project. Claude Code loads it when a task matches its description.
How do I install Survey Design in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill survey-design -a codex`. Or copy the skill folder (design-research/skills/survey-design in Owl-Listener/designer-skills) into .agents/skills/survey-design in your project. Codex loads it when a task matches its description.
Can I use Survey Design in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill survey-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/survey-design, .gemini/skills/survey-design, .github/skills/survey-design and .opencode/skills/survey-design in your project.
What does Survey Design need to run?
SKILL.md names no scripts, command-line tools or credentials: Survey Design is instructions for the agent only.
Does Survey Design access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Survey Design safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Survey Design use?
Survey Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Survey Design use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Survey Design?
Skills that share tags, products or a category with Survey Design: Design Sprint (wondelai/skills, 2.4k stars), Loki Mode (davila7/claude-code-templates, 33k stars), Messaging Ab Tester (gooseworks-ai/goose-skills, 1.2k stars) and Measure Survey Analysis (product-on-purpose/pm-skills, 716 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Survey Design?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.