dragoon0x/everything-design-taste

survey-design

Designing user surveys, question types, response bias, and survey analysis.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill survey-design

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,137 B
  • docs SUMMARY.md 96 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Survey Design

Question Types

Type When Example
Likert scale Measure agreement/satisfaction 'Rate your experience (1-5)'
Multiple choice Categorical data 'Which feature do you use most?'
Open-ended Qualitative insight 'What would you improve?'
NPS Loyalty measurement 'How likely to recommend? (0-10)'
Matrix Multiple items on same scale Rate [features] on [satisfaction]

Rules

  1. Keep it short (5-10 questions, 3-5 minutes)
  2. One question per question (no double-barreled)
  3. Neutral wording (no leading questions)
  4. Logical order (general → specific)
  5. Required questions sparingly (let people skip)
  6. Mobile-friendly (most surveys are completed on phones)
  7. Thank respondents meaningfully

Avoiding Bias

  • Randomize option order
  • Include 'N/A' or 'Other' options
  • Don't ask about features they haven't used
  • Avoid 'How much do you love our product?' (leading)