customer-story-builder
Take raw customer inputs — interview transcripts, survey responses, Slack quotes, support tickets, review excerpts — and generate a structured case study draft with problem/solution/result narrative, pull-quotes, metric callouts, and multi-format outputs (full case study, one-pager, social proof snippet, sales deck slide). Pure reasoning skill. Use when a product marketing team has customer signal but no time to write the story.
npx skills add gooseworks-ai/goose-skills --skill customer-story-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Customer Story Builder Turn raw customer signal into a polished case study — plus every derivative format you need. One input (messy transcript or quote), all outputs (case study, one-pager, social snippet, deck slide). **Core principle:** The best customer stories already exist in your support tickets, Slack channels, and call recordings. You just need to extract and structure them. ## When to Use - "Turn this customer interview into a case study" - "We have a great Slack quote from [customer] — help me build a story around it" - "Write a case study for [customer]" - "I need social proof assets from [customer win]" - "Package this customer result for the sales team" ## Phase 0: Intake ### Customer Context 1. **Customer name** — Can we use their name publicly? (Named vs. anonymous) 2. **Company description** — Industry, size, stage (1 sentence) 3. **Customer role/title** — Who's the champion? 4. **How long have they been a customer?** ### Raw Input (provide any/all) 5. **Interview transcript** — Full or partial transcript from a customer call 6. **Slack/email quotes** — Specific messages where they praised the product 7. **Survey responses** — NPS comments, CSAT feedback 8. **Sup
- When to Use
- Phase 0: Intake
- Customer Context
- Raw Input (provide any/all)
- Story Angle
- Phase 1: Extract Story Elements
- The Problem (Before)
- The Decision (Why You)
- The Solution (How)
- The Result (After)
- Best Quotes
- Phase 2: Generate Story Outputs
- Output 1: Full Case Study (800-1200 words)
- Output 2: One-Pager (Sales Leave-Behind)
What does the customer-story-builder skill do?
Take raw customer inputs — interview transcripts, survey responses, Slack quotes, support tickets, review excerpts — and generate a structured case study draft with problem/solution/result narrative, pull-quotes, metric callouts, and multi-format outputs (full case study, one-pager, social proof snippet, sales deck slide). Pure reasoning skill. Use when a product marketing team has customer signal but no time to write the story.
How do I install it?
Run `npx skills add gooseworks-ai/goose-skills --skill customer-story-builder --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 gooseworks-ai/goose-skills, a repository with 1,091 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.