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.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%

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

The skill is highly actionable with a clear sequenced workflow and an explicit quality-check checkpoint, and it stays lean without explaining concepts Claude already knows. Its only gap is progressive disclosure: a long single file where the detailed output templates could be split into referenced materials.

Suggestions

Move the five Phase 2 output templates (full case study, one-pager, social snippets, deck slide, metric cards) into a referenced file such as references/output-templates.md, leaving SKILL.md as a concise overview that signals the reference.

Remove the duplicated 'Trigger Phrases' section at the end, since 'When to Use' already covers the same invocation cues and the description frontmatter carries the triggers.

Drop or compress the 'Cost' and 'Tools Required' sections (both essentially say the skill is free and tool-less) to tighten the tail of the document.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding about what a case study is; templates and checklists are the actionable core and every section earns its place, assuming Claude's competence.	3 / 3
Actionability	Provides copy-paste-ready output templates with placeholders, exact intake fields, named file paths, and word-count targets — concrete, executable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	A clear Phase 0 (Intake) → Phase 1 (Extract) → Phase 2 (Generate) → Phase 3 (Quality Check) → Phase 4 (Output) sequence with an explicit validation checkpoint (the Phase 3 quality checklist).	3 / 3
Progressive Disclosure	It is a single well-organized file with no nested references, but at ~230 lines the five substantial inline output templates (Phase 2) are content that could be deferred to separate reference files to keep SKILL.md a leaner overview.	2 / 3
	Total	11 / 12 Passed

Description

100%

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

The description is specific, trigger-rich, and complete with an explicit 'Use when' clause in third-person imperative voice. It clearly conveys both capability and invocation context with no vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and inputs ("interview transcripts, survey responses, Slack quotes, support tickets, review excerpts") plus specific outputs ("problem/solution/result narrative, pull-quotes, metric callouts... full case study, one-pager, social proof snippet, sales deck slide"), matching the multi-action anchor.	3 / 3
Completeness	Clearly answers both what (take raw inputs and generate structured case study drafts/derivatives) and when via an explicit "Use when a product marketing team has customer signal but no time to write the story."	3 / 3
Trigger Term Quality	Covers natural terms a product marketer would actually say ("case study", "one-pager", "social proof snippet", "sales deck slide", "interview transcripts") with good variation, not jargon.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (customer-story/case-study generation from raw customer signal) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/content/composites/customer-story-builder/SKILL.md
Commit: 8866b2a

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.