Community

case-studies

Open Agent Skill · writing · works with Claude Code, Codex, Cursor, and compatible agents

Write customer case studies with problem, solution, proof, and quote discipline. Use whenever the user asks for a case study, customer success story, proof point for sales, or customer story for the website.

View on GitHub

Case Studies

Case studies are evidence. Structure: challenge → solution → results → quote. If metrics or quotes are missing, mark placeholders — do not fabricate.

Structure

# <Customer> achieves <outcome> with <Product>

## At a glance
- Industry / size
- Use case
- Results (only verified)

## Challenge
## Solution
## Results
## Quote
## About <Customer>

Rules

  1. Never invent logos, quotes, or percentages.
  2. Prefer specific metrics user provides; else qualitative outcomes labeled.
  3. Get approval path noted when legal/customer marketing review required.
  4. Avoid feature dumps; tie capabilities to the challenge.
  5. SEO titles only if requested; accuracy first.
  6. Offer short (1-pager) and long versions when useful.

Edge cases

  • Anonymous customer: still need verifiable internal proof.
  • Early startup metrics tiny: honesty over hype.
  • Multi-product story: one narrative thread.