Every marketer knows they need more case studies. Nobody wants to write them. This skill takes the raw ingredients — customer name, problem, solution, results — and structures them into a publish-ready case study with pull quotes, metric callouts, and a CTA section.
What Makes This a Claude Code Skill
Claude Code reads your project’s existing case studies (if any) to match tone and format. It structures the raw inputs into a situation-problem-solution-result narrative, generates pull quotes from the metrics, and outputs both a long-form version and a short testimonial snippet you can use on landing pages, emails, or social.
The command file lives at .claude/commands/case-study.md.
What Gets Generated
- Full case study in situation → problem → solution → results format
- Headline that leads with the result, not the customer name
- Pull quotes built from the strongest metrics
- Metric callout boxes for key numbers (e.g., “+42% open rate in 3 weeks”)
- CTA section connecting the case study to your product
- Short testimonial snippet (2-3 sentences) for reuse on landing pages and emails
Setup
Create .claude/commands/case-study.md:
Write a case study from these inputs: $ARGUMENTS
Expected input format (any order):
- Customer name or company
- Their situation before
- The problem they faced
- What solution they used (your product/service)
- Results with specific metrics
## Step 1: Existing Format Check
Read any existing case studies in the project to match:
- Tone and voice
- Formatting conventions
- Section structure
- CTA style
## Step 2: Narrative Structure
Write the case study following this flow:
1. **Headline**: Lead with the result (e.g., "How Acme Co Increased Email Open Rates by 42% in 3 Weeks")
2. **The Situation**: Who is the customer? What do they do? Set the context.
3. **The Problem**: What was broken or underperforming? Use specific numbers if available.
4. **The Solution**: What did they implement? How did it work? Keep this section focused on the approach, not a feature list.
5. **The Results**: Lead with the biggest number. Include before/after comparisons. Be specific.
6. **What's Next**: Brief forward-looking statement about continued use or expansion.
## Step 3: Supporting Elements
Generate:
- 2-3 pull quotes (formatted as blockquotes) that highlight key metrics or insights
- Metric callout boxes for the 2-3 most impressive numbers
- A CTA section that connects the story to your product/service
## Step 4: Short Snippet
Write a 2-3 sentence testimonial-style snippet that works standalone on:
- Landing pages
- Email signatures
- Social media posts
- Sales decks
## Output
Write full case study to `./case-studies/[customer-name]-case-study.md`
Write short snippet to terminal.Usage
/project:case-study "Customer: Acme Co. Problem: low email open rates, 12% average. Solution: AI subject line testing with our platform. Results: 42% open rate in 3 weeks, 3x click-through improvement."Claude structures the raw inputs into a full narrative case study and a reusable testimonial snippet.
Tips
- The messier the input, the more Claude fills in — but specific metrics always make a better case study
- Run the output through Anti-AI Rewrite before publishing
- Keep a running folder of case studies — they compound in value as sales collateral