Agent skill
case-study-doc
Format a client result into a shareable case study document. Structure follows Client Background → The Challenge → What We Did → The Results → Key Takeaways. 500-800 words. Professional, results-focused, quotable. Use when user needs a "case study", "client success story", "results document", or "portfolio piece".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/case-study-doc
SKILL.md
Load Context First
Before executing this skill, read the following files from the project folder if they exist:
- USER.md — who the user is, how they think, how they work
- BUSINESS.md — their business, products, positioning, brand voice, content strategy
- ICP.md — their ideal customer, their language, their fears, what makes them buy
- Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
- Any additional context provided by the user in this session
Use all context silently. Do not reference or summarize files unless asked.
Case Study Document
Purpose: Turn a client result into a professional, shareable case study (500-800 words) that can be used on websites, in proposals, and as sales collateral.
Structure
# [Headline: Result-Focused]
*[Subheadline: Client type + specific outcome]*
---
## Client Background
**Client:** [Name or anonymized description — e.g., "B2B SaaS Founder"]
**Industry:** [Industry]
**Size:** [Team size or revenue range if relevant]
[2-3 sentences about the client: who they are, what they do, and relevant context for the case study.]
---
## The Challenge
[3-5 sentences describing the specific problem the client faced. Use concrete details:]
- What wasn't working
- What they'd already tried
- What was at stake (money, time, opportunity cost)
- Why this problem mattered to their business
---
## What We Did
[Description of the solution — 150-250 words]
**Our approach:**
1. **[Phase/Step 1]** — [What was done and why]
2. **[Phase/Step 2]** — [What was done and why]
3. **[Phase/Step 3]** — [What was done and why]
[Include enough detail to be credible without revealing proprietary methods]
---
## The Results
**Headline metric:** [The most impressive number — big and bold]
| Metric | Before | After | Change |
|--------|--------|-------|--------|
| [Metric 1] | [Value] | [Value] | [+/-X%] |
| [Metric 2] | [Value] | [Value] | [+/-X%] |
| [Metric 3] | [Value] | [Value] | [+/-X%] |
**Timeline:** [How long it took to achieve these results]
[Optional: Client quote about the experience or results]
> "[Quote from client about the impact]" — [Client Name/Title]
---
## Key Takeaways
1. **[Takeaway 1]** — [One sentence explanation]
2. **[Takeaway 2]** — [One sentence explanation]
3. **[Takeaway 3]** — [One sentence explanation]
---
*[Optional CTA: "Want similar results? [Contact/link]"]*
Quality Checklist
- Headline leads with the result (not the process)
- Client details are accurate (or properly anonymized)
- Challenge section is relatable (reader sees themselves)
- Solution is specific enough to be credible
- Results include real numbers with before/after
- Timeline included (results without timing context are weak)
- 500-800 words total
- Professional tone — suitable for website or proposal
- No fabricated metrics or quotes
- Key takeaways are transferable (not just "hire us")
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?