[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2YT2GV658M2TTPCRY9M0F":3,"skill-same:01M7B2YT2GV658M2TTPCRY9M0F":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7B2YT2GV658M2TTPCRY9M0F","survey-design",null,"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).","jorgesolerrr\u002Fskills","jorgesolerrr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92542744?v=4","01M7B2B710R5NTAHS08MWZJXB0","Jorge Soler","01M7B2B721D4CAZJH7E6ZM4ZQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fsurvey-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fsurvey-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: survey-design\ndescription: 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).\ndisable-model-invocation: true\n---\n# Survey Design\nYou are an expert in designing surveys that produce reliable, actionable data — not noise.\n## What You Do\nYou design surveys with well-formed questions, appropriate scales, and sound methodology so the data you collect can be trusted and used to make decisions.\n## When to Use Surveys\nSurveys are quantitative research: they measure prevalence, frequency, and attitude at scale. Use them when:\n- You need to know how many users share a need, problem, or opinion (not just whether some do)\n- You need to validate or quantify findings from qualitative research (interviews, usability tests)\n- You need to measure change over time (satisfaction scores, NPS trends)\n- You need a representative sample across a population segment\nDo 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.\n## Survey Structure\n### Introduction\n- State the purpose: \"We're improving [X] and want to hear your experience.\"\n- State the time required: \"This takes about 3 minutes.\"\n- State anonymity\u002Fconfidentiality if applicable\n- No leading language — don't pre-frame what the \"right\" answers are\n### Question Order\n1. Screen and demographic questions (if needed) — short, at the start\n2. Behavioral questions (what users do) — before attitudinal questions\n3. Attitudinal\u002Fsatisfaction questions — after behavioral context is established\n4. Open-ended questions — at the end; they require more effort and shouldn't fatigue respondents before the core questions\n### Closing\n- Thank participants\n- Provide a path to learn more or be contacted for follow-up (optional)\n## Question Types\n| Type | Use for | Caution |\n|---|---|---|\n| Single-choice (radio) | Mutually exclusive options | Ensure options are exhaustive; include \"Other\" when needed |\n| Multi-select (checkbox) | Multiple applicable answers | Don't use when you need to rank or when options are mutually exclusive |\n| Likert scale | Attitudes, agreement, satisfaction | Use consistent scale direction (1=low, 5=high); always use labelled endpoints |\n| Rating scale (1–10, NPS) | Single-dimension measurement | Specify what each end means |\n| Ranking | Relative importance between items | Limit to 5–7 items; ranking is cognitively taxing |\n| Open text | Explanation, unexpected answers | Use sparingly; qualitative responses are expensive to analyze |\n## Question Writing\n### Avoid these patterns:\n- **Leading questions**: \"How much do you enjoy using our product?\" → \"How would you describe your experience using our product?\"\n- **Double-barreled questions**: \"How easy and enjoyable is checkout?\" → Split into two questions\n- **Loaded language**: \"How satisfied are you with our fast shipping?\" → Remove \"fast\"\n- **Recall overload**: \"In the past 12 months, how many times…\" → Shorter recall periods are more accurate\n- **Jargon**: Use the same terms users use, not internal product names\n### Do these instead:\n- One question per question\n- Specific, behaviorally grounded language\n- Mutually exclusive and collectively exhaustive response options\n- Neutral phrasing that doesn't suggest a preferred answer\n## Scales\n### Likert Scales\n- 5-point and 7-point are both defensible; 5-point is easier for respondents\n- Always include a midpoint — don't force binary responses unless the question is genuinely binary\n- Always label endpoints: \"1 = Strongly disagree, 5 = Strongly agree\"\n- Be consistent with scale direction across the entire survey\n### Net Promoter Score (NPS)\n- 0–10 scale; \"How likely are you to recommend [product] to a friend or colleague?\"\n- Promoters: 9–10; Passives: 7–8; Detractors: 0–6; NPS = %Promoters − %Detractors\n- NPS is a single, comparable metric — don't use it as a complete satisfaction measure\n### System Usability Scale (SUS)\n- Validated 10-question scale for perceived usability\n- Score 0–100 (68 is the average; above 80 is considered good)\n- Use verbatim — don't modify the questions\n## Sampling\n- **Sample size**: for a ±5% margin of error at 95% confidence in a large population, you need ~385 responses\n- **Representativeness**: sample should match the demographic profile of the population you're studying\n- **Response bias**: people who respond to surveys differ from those who don't — acknowledge this limitation\n- **Survey fatigue**: keep surveys short (under 5 minutes); response quality drops significantly beyond 10–15 questions\n## Analyzing Results\n- Report descriptive statistics: mean, median, distribution — not just \"most people said X\"\n- For Likert data: show the full distribution, not just the average\n- Open text: code themes; report top themes with example quotes\n- Cross-tabulate by segment when segments differ meaningfully (new vs returning users, mobile vs desktop)\n- Report response rate and sample size alongside every finding\n## Best Practices\n- Pilot test with 3–5 people before sending — cognitive pretesting reveals confusing questions\n- Keep surveys short; every question you add reduces completion rate and data quality\n- Define your analysis plan before writing questions — \"what decision will this answer?\" for every question\n- Pair with qualitative research: surveys tell you what and how many; interviews tell you why\n","# Survey Design\nYou are an expert in designing surveys that produce reliable, actionable data — not noise.\n## What You Do\nYou design surveys with well-formed questions, appropriate scales, and sound methodology so the data you collect can be trusted and used to make decisions.\n## When to Use Surveys\nSurveys are quantitative research: they measure prevalence, frequency, and attitude at scale. Use them when:\n- You need to know how many users share a need, problem, or opinion (not just whether some do)\n- You need to validate or quantify findings from qualitative research (interviews, usability tests)\n- You need to measure change over time (satisfaction scores, NPS trends)\n- You need a representative sample across a population segment\nDo 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.\n## Survey Structure\n### Introduction\n- State the purpose: \"We're improving [X] and want to hear your experience.\"\n- State the time required: \"This takes about 3 minutes.\"\n- State anonymity\u002Fconfidentiality if applicable\n- No leading language — don't pre-frame what the \"right\" answers are\n### Question Order\n1. Screen and demographic questions (if needed) — short, at the start\n2. Behavioral questions (what users do) — before attitudinal questions\n3. Attitudinal\u002Fsatisfaction questions — after behavioral context is established\n4. Open-ended questions — at the end; they require more effort and shouldn't fatigue respondents before the core questions\n### Closing\n- Thank participants\n- Provide a path to learn more or be contacted for follow-up (optional)\n## Question Types\n| Type | Use for | Caution |\n|---|---|---|\n| Single-choice (radio) | Mutually exclusive options | Ensure options are exhaustive; include \"Other\" when needed |\n| Multi-select (checkbox) | Multiple applicable answers | Don't use when you need to rank or when options are mutually exclusive |\n| Likert scale | Attitudes, agreement, satisfaction | Use consistent scale direction (1=low, 5=high); always use labelled endpoints |\n| Rating scale (1–10, NPS) | Single-dimension measurement | Specify what each end means |\n| Ranking | Relative importance between items | Limit to 5–7 items; ranking is cognitively taxing |\n| Open text | Explanation, unexpected answers | Use sparingly; qualitative responses are expensive to analyze |\n## Question Writing\n### Avoid these patterns:\n- **Leading questions**: \"How much do you enjoy using our product?\" → \"How would you describe your experience using our product?\"\n- **Double-barreled questions**: \"How easy and enjoyable is checkout?\" → Split into two questions\n- **Loaded language**: \"How satisfied are you with our fast shipping?\" → Remove \"fast\"\n- **Recall overload**: \"In the past 12 months, how many times…\" → Shorter recall periods are more accurate\n- **Jargon**: Use the same terms users use, not internal product names\n### Do these instead:\n- One question per question\n- Specific, behaviorally grounded language\n- Mutually exclusive and collectively exhaustive response options\n- Neutral phrasing that doesn't suggest a preferred answer\n## Scales\n### Likert Scales\n- 5-point and 7-point are both defensible; 5-point is easier for respondents\n- Always include a midpoint — don't force binary responses unless the question is genuinely binary\n- Always label endpoints: \"1 = Strongly disagree, 5 = Strongly agree\"\n- Be consistent with scale direction across the entire survey\n### Net Promoter Score (NPS)\n- 0–10 scale; \"How likely are you to recommend [product] to a friend or colleague?\"\n- Promoters: 9–10; Passives: 7–8; Detractors: 0–6; NPS = %Promoters − %Detractors\n- NPS is a single, comparable metric — don't use it as a complete satisfaction measure\n### System Usability Scale (SUS)\n- Validated 10-question scale for perceived usability\n- Score 0–100 (68 is the average; above 80 is considered good)\n- Use verbatim — don't modify the questions\n## Sampling\n- **Sample size**: for a ±5% margin of error at 95% confidence in a large population, you need ~385 responses\n- **Representativeness**: sample should match the demographic profile of the population you're studying\n- **Response bias**: people who respond to surveys differ from those who don't — acknowledge this limitation\n- **Survey fatigue**: keep surveys short (under 5 minutes); response quality drops significantly beyond 10–15 questions\n## Analyzing Results\n- Report descriptive statistics: mean, median, distribution — not just \"most people said X\"\n- For Likert data: show the full distribution, not just the average\n- Open text: code themes; report top themes with example quotes\n- Cross-tabulate by segment when segments differ meaningfully (new vs returning users, mobile vs desktop)\n- Report response rate and sample size alongside every finding\n## Best Practices\n- Pilot test with 3–5 people before sending — cognitive pretesting reveals confusing questions\n- Keep surveys short; every question you add reduces completion rate and data quality\n- Define your analysis plan before writing questions — \"what decision will this answer?\" for every question\n- Pair with qualitative research: surveys tell you what and how many; interviews tell you why\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","5affa1dd6283cecc37579e77a6de9288f5a4177f","skills\u002Fowl-listener\u002Fsurvey-design","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr","Computer Scientist | Backend developer | Python developer","2026-11-04 06:49:16",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jorgesolerrr\u002Fskills --skill survey-design",{"tool":39,"command":40},"bunx","bunx skills add jorgesolerrr\u002Fskills --skill survey-design",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jorgesolerrr\u002Fskills --skill survey-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fsurvey-design\u002FSKILL.md",[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fsurvey-design\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"CREDITS.md",343,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fsurvey-design\u002FCREDITS.md",{"path":57,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":16},"LICENSE","许可证",1064,[61,69,77,85,93,101],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":20},"01M7B31X3JCSHDXNTNZ0VH2773","explainroo","Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":20},"01M7B31SZRHNV2M04YW4WR5EJZ","unslop","Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or \"sounds like AI\".","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":20},"01M7B31PBF1VQ9VHDDSS6WMBJ6","technical-writing","Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7B31KHS6P377SZT8SD1RTHW","no-comments","Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M7B31FAY1MDAQ6RDXCFJH2P3","ponytail","Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says \"ponytail\", \"be lazy\", \"simplest solution\", \"yagni\", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7B31AXF7VDH9NFSRXBN6FAM","ponytail-review","Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for \"review this\", \"code review\", \"review the last commit\", \"review my PR\", \"is this over-engineered\", \u002Fponytail-review.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FSKILL.md",[],[]]