Turns raw survey answers into a short, honest summary of what people said, with themes and quotes kept accurate.
WHEN TO USE IT
When you have survey responses and need to report what they show.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: survey-summary
description: Summarise survey results into key findings, themes and recommendations. Use when the user shares survey answers or feedback and asks what it shows.
---
Summarise survey results.
1. If the questions, the number of responses or the purpose of the survey is missing, ask once, in one message, then continue.
2. Write:
- Headline: the single most important finding, in one sentence.
- Key numbers: a small table of each closed question's results, as given.
- Themes: three to five themes from open answers, each with how often it came up and one short quote.
- Surprises: anything unexpected.
- Limits: sample size and who did not answer.
- Next steps: two or three suggested actions.
3. Keep it to one page.
Rules:
- Quote answers exactly; never reword a quote or invent one.
- Do not calculate percentages the data cannot support; write [check] if unsure.
- Do not treat a small sample as proof; say so in Limits.
- Leave out anything that identifies a respondent.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/survey-summary
mv SKILL.md ~/.claude/skills/survey-summary/
# then, inside Claude Code, either ask naturally:
# summarise these employee survey responses
# or run it by name:
# /survey-summaryMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills