write-survey

Drafts and audits self-administered surveys using NN/g best practices and a per-question bias lint.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-survey-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-survey
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/write-survey
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-survey-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Surveys are easy to write and easy to get wrong: leading stems, double-barreled questions, unbalanced scales, and prediction questions produce data that cannot support the claims teams make from it. This Skill turns research questions into a short, bias-linted, correctly-scaled survey matched to the right design-cycle stage. ## Core Features & Use Cases - Survey-type matching: Maps nine survey types (discovery, SEQ, SUS, NPS/CSAT/CES, intercept, and more) onto the Discover-Explore-Test-Listen cycle, fixing deployment channel, length budget, and what results may claim. - Scale construction: Decides Likert vs. semantic differential per construct and enforces balanced anchors, odd point counts, labeled endpoints, and consistent direction. - Ten-rule bias audit (S1-S10): Detects and rewrites acquiescence, social desirability, framing, double-barreled, prediction, unbalanced scales, non-exhaustive options, missing opt-outs, order effects, and fatigue. - Use Case: A stakeholder hands you "just ask users if they'd pay for it." The audit flags it as a prediction question (S5), replaces it with a past-behavior item, and ships a soft-launch-ready survey with a full bias audit table. ## Quick Start Draft a short in-app post-booking survey for my beta app and audit each question for bias before I send it.

Frequently Asked Questions about write-survey

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a UX survey without bias?

Run every question through a bias lint covering acquiescence, social desirability, framing, double-barreled items, prediction, unbalanced scales, non-exhaustive options, missing opt-outs, order effects, and fatigue. One violation means rewrite, then soft-launch to a small sample before the full send.

Should I use a Likert scale or semantic differential in my survey?

Use semantic differential by default when rating a thing along a dimension like easy versus difficult, since it reduces acquiescence and social-desirability bias. Reserve Likert agree-disagree statements for genuine attitude constructs that cannot be phrased as a bipolar pair.

Can I reword SUS or NPS questions to fit my product?

No. Standardized instruments like SUS, SEQ, NPS, CSAT, and CES must ship verbatim because their only value is score comparability against benchmarks. Reworded SUS is not SUS, so choose verbatim or fully custom, never in between.

Why shouldn't I ask users "would you pay for this feature"?

People cannot predict their own behavior, so stated-intent answers are noise. Ask about past or current behavior instead, such as whether they paid for something similar in the last three months, or flag any surviving intent item as under-evidenced rather than reporting it as demand.

When is a survey the wrong research method?

A survey measures attitudes and self-reported behavior at scale; it cannot observe what people actually do or explain why. If the research question is about why something happens or whether users can complete a task, use interviews or usability testing instead.