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

83%

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

81%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 well-structured, self-contained reasoning skill with clear phased workflow, concrete multi-format output templates, and an explicit quality-check checkpoint. It is lean and actionable with only minor verbosity in the intake and trigger-phrase sections.

Suggestions

Tighten the Phase 0 intake checklist and the duplicate 'When to Use'/'Trigger Phrases' sections to reduce token overlap.

Add a short explicit 'validate the extracted quotes against the source before drafting' checkpoint in Phase 1 to strengthen the feedback loop.

Resolve the output-template placeholders (e.g. '[Metric 1]') with a one-line instruction on how to fill them from the Phase 1 extraction, improving copy-paste actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with well-organized intake/extraction/output phases and template scaffolding that earns its tokens, though the Phase 0 intake checklist and repeated trigger-phrase sections add some length that could be trimmed without loss.	4 / 5
Actionability	Provides concrete, copy-paste-ready output templates for all five formats plus a quality checklist and explicit save paths, with only minor gaps (e.g., placeholder fields like '[Metric 1]' are guided but not fully resolved by instruction).	4 / 5
Workflow Clarity	Phases 0–4 give a clear linear sequence with an explicit Phase 3 quality-check checkpoint including permission/freshness flags; it is not a destructive or batch operation, so the missing formal validate-then-retry loop does not trigger the cap, though checkpoint enforcement is softer than the 5-anchor.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets directories absent), so all content lives correctly inline in a single well-sectioned SKILL.md with clear headers and no nested references — appropriate for a self-contained reasoning skill.	5 / 5
	Total	17 / 20 Passed

Description

85%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 strong description that explicitly states both what the skill does and when to use it, with a rich, concrete list of inputs and output formats. It is specific and actionable with only minor room to sharpen trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '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)' — giving comprehensive coverage of what the skill produces.	5 / 5
Completeness	Clearly answers 'what' (the generation of structured case studies and derivative formats) and 'when' with an explicit 'Use when a product marketing team has customer signal but no time to write the story' trigger clause.	5 / 5
Trigger Term Quality	Strong natural terms ('customer inputs', 'interview transcripts', 'survey responses', 'Slack quotes', 'support tickets', 'case study', 'social proof', 'sales deck slide') that users would plausibly say, though it leans on one paraphrased trigger clause rather than a compact battery of synonymous keyword variants.	4 / 5
Distinctiveness Conflict Risk	The case-study / customer-story niche is fairly distinct and the input types (transcripts, Slack quotes, support tickets) are specific, but the broad 'content' tag and marketing-copy framing leave minor overlap risk with general copywriting skills.	4 / 5
	Total	18 / 20 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: 2523432

Reviewed: 7 days 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.