Agent skill

measure-survey-analysis

Analyze survey results into actionable PM insights. Produces persona segmentation, hypothesis validation status, thematic clustering of open-text responses, statistical confidence labels, prioritized recommendations, and what-NOT-to-conclude warnings. Refuses to overstate statistical significance from weak samples or biased instruments.

product-on-purposegithub.com/product-on-purposeGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add product-on-purpose/pm-skills --skill measure-survey-analysis --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 12 KB
Bundled scripts: none
Version: 1.2.0
Declared author: product-on-purpose
Path: skills/measure-survey-analysis/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 518
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Survey Analysis You analyze survey results into actionable PM insights. Your job is to (a) honestly characterize what the data shows, (b) flag what it does NOT show, (c) identify themes in open-text responses, (d) connect findings to hypotheses, and (e) produce prioritized recommendations. ## Identity - Phase skill (measure); Triple Diamond integration - Single-turn lifetime; produces one analysis artifact per invocation - Read-only tools (Read, Grep); produces markdown output - Pairs with `discover-interview-synthesis` as the qualitative complement to this quantitative analysis ## Core principle **Honesty about what the data does NOT show is more valuable than confident conclusions from weak data.** Most surveys have biased samples, leading questions, or insufficient response counts. Your job is to make the limitations explicit and to refuse overstating statistical significance. A 90-percent confidence claim from 47 responses on a 5-question survey with a leading question is worse than no claim at all. You explain why and offer what would change the analysis. ## When NOT to Use - Your data is inter

What's inside
Steps it walks through
  1. Identity
  2. Core principle
  3. When NOT to Use
  4. Inputs
  5. What you produce
  6. 1. Executive summary (3-5 sentences)
  7. 2. Survey methodology summary
  8. 3. Per-question analysis
  9. 4. Persona / segment breakdown
  10. 5. Open-text response thematic clustering
  11. 6. Hypothesis validation
  12. 7. What the data does NOT show (limitations)
  13. 8. Prioritized recommendations
  14. 9. Next steps
Ships with 4 files
  • HISTORY.md
  • evals/trigger-fixtures.json
  • references/EXAMPLE.md
  • references/TEMPLATE.md
More from pm-skills
All skills →
About this skill
What does the measure-survey-analysis skill do?

Analyze survey results into actionable PM insights. Produces persona segmentation, hypothesis validation status, thematic clustering of open-text responses, statistical confidence labels, prioritized recommendations, and what-NOT-to-conclude warnings. Refuses to overstate statistical significance from weak samples or biased instruments.

How do I install it?

Run `npx skills add product-on-purpose/pm-skills --skill measure-survey-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going