CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

survey-design

Writing or reviewing a survey or questionnaire: customer feedback, NPS, CSAT, CES, pricing, market research, an in-app survey. Starts from the decision, asks about facts, pilots it, and reports the sample honestly.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable instruction skill: concrete question templates, explicit sequencing with pilot and quality-check validation loops, and a success-verification section. The only notable deductions are the mildly promotional live-poll tool paragraph and a single-file structure slightly beyond lean overview size.

DimensionReasoningScore

Conciseness

The body is dense, prescriptive craft guidance Claude does not reliably hold (question ordering rules, option-range construction, quality-check thresholds like "roughly 5% of completes to be poor"), with almost no filler or explanation of known concepts. Not a 5 because the live-poll paragraph spends several lines promoting AskOne ("People answer on their phones with no account: choice polls, ratings, word clouds and quizzes...") with a UTM-tagged link, which is trimmable.

4 / 5

Actionability

For an instruction-only skill, guidance is copy-paste ready: exact question wordings with full response option sets ("When using [product/feature] to [task], how much effort did you personally have to put in?" Very low / Low / Moderate / High / Very high effort), weak-vs-better rewrites, concrete option ranges ("0 / 1–2 / 3–4 / 5 or more"), and a numbered output deliverable list. Specific examples cover the common cases (CES, CSAT, NPS, JTBD).

5 / 5

Workflow Clarity

The end-to-end process is clearly sequenced — decision and research questions ("Every survey question maps to a research question, or it goes"), sample selection, pre-interviews, pilot ("what would change the survey"), sending, analysis, and reporting — with explicit validation in "Pilot it with a small group before sending it to everyone", quality-check handling with a feedback loop ("flag the responses that fail several checks, look at them, exclude on criteria you state, and report how many"), and a success-verification checklist ("How you can tell it worked"). Not a 4 because checkpoints are explicit rather than implied.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and all ~90 lines live in one well-sectioned SKILL.md with clear headers (Is it a survey at all? / Before writing a question / Writing the questions / Templates / Output). Not a 5 because the body exceeds the under-50-line simple-skill exception and content like the templates and further-reading links is inline with no quick-start overview or split files.

4 / 5

Total

18

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, keyword-rich description with a clear capability list, but it lacks an explicit "Use when..." trigger clause, leaving the activation condition only implied. Adding an explicit trigger sentence and a few synonym terms (poll, feedback form) would raise completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating, reviewing, or analyzing a survey, questionnaire, NPS/CSAT/CES measure, or in-product feedback prompt."

Include common synonyms users might say, such as "poll", "feedback form", or "customer satisfaction survey", to broaden natural trigger coverage.

Consider naming the review use case's trigger explicitly (e.g. "or when the user shares a survey draft for critique") since "reviewing" currently has no activation phrasing.

DimensionReasoningScore

Specificity

"Writing or reviewing a survey or questionnaire" plus "Starts from the decision, asks about facts, pilots it, and reports the sample honestly" names several concrete actions (write, review, pilot, report sample), and enumerates concrete survey types (NPS, CSAT, CES, pricing, market research, in-app survey). Not a 5 because "asks about facts" and "reports the sample honestly" describe posture rather than concrete actions.

4 / 5

Completeness

The "what" is clear ("Writing or reviewing a survey or questionnaire" with a concrete type list), but there is no explicit "Use when..." clause or equivalent trigger guidance — the "when" is only weakly implied by the opening gerund phrase, which caps completeness at 3 per the rubric guideline. Not a 2 because the "what" is detailed and specific, not vague.

3 / 5

Trigger Term Quality

Strong natural keywords users would actually say: "survey", "questionnaire", "customer feedback", "NPS", "CSAT", "CES", "pricing", "market research", "in-app survey". Not a 5 because common variants like "poll", "feedback form", or "customer satisfaction survey" are absent.

4 / 5

Distinctiveness Conflict Risk

The survey-design niche (questionnaire design, NPS/CSAT/CES measures, sampling and pilots) is clearly distinct with domain-specific trigger terms. Not a 5 because "customer feedback" and "pricing" overlap mildly with adjacent research skills (interviewing, sentiment analysis, pricing analysis).

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-market-research/skills/survey-design/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.