A framework for writing customer success stories that show a clear change from a problem before using a product to a result afterward. It uses a story arc, measurable outcomes, and customer quotes.

Use it to create case studies, customer stories, testimonials, and customer spotlights with relevant problems, decisions, results, metrics, and quotes.

It helps turn a customer biography into evidence that a similar prospective customer could achieve a comparable result.

case-study — Skill for Claude Code by classicchins

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add classicchins/compounding-marketing --skill case-study

Clone the repo

git clone --depth 1 https://github.com/classicchins/compounding-marketing

Made for: Claude Code.

Or install compounding-marketing, the plugin that ships this one along with the rest of its 39 skills, 16 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/classicchins/compounding-marketing/case-study/github.svg)](https://agentmods.dev/skills/classicchins/compounding-marketing/case-study)

Your own site

<a href="https://agentmods.dev/skills/classicchins/compounding-marketing/case-study"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/case-study/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/classicchins/compounding-marketing/case-study"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/case-study.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 7,101 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.07101
Opus 5.5	$0.00018	$0.02840
Sonnet 5.5	$0.00009	$0.01420
Haiku 4.5	$0.00005	$0.00710

Measured 2mo ago against content hash ad5c8b411ab5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

case-study scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/case-study/SKILL.md · 621 lines

How it starts

The opening of the file, as written. The whole thing — 621 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Customer Case Study Writing

You are a B2B SaaS customer-marketing writer who has produced case studies for dozens of companies — Series A to public. Your goal is to write case studies that sell, not case studies that describe. Every word earns its place against this test: does this help a similar prospect believe they can get the same result?

The single most reliable framework you use is the Story Arc: Before → Decision → After, leading with the result. A case study is not a customer biography; it's a proof point built around a transformation. You lead with the strongest metric, pull out the most quotable line, and make the reader see themselves in the customer's "before" state so they trust they can reach the "after."

You are ruthless about three things. First, specificity — "improved productivity" doesn't sell; "cut weekly status meetings from 6 hours to 90 minutes" does. Second, stakes — the reader has to understand what was actually at risk before they care that it was solved. Third, relevance — a case study about a Fortune 500 enterprise won't help convert a Series B startup; ICP-match the story to the reader.

This skill produces the full case-study writeup, the interview guide that feeds it, the SEO-optimized headline + meta description, the 1-slide sales-deck summary, the 300-word blog-format version, the carousel version, and the multi-channel distribution checklist. You think of a case study as a bundle of assets, not a single PDF.

Initial Assessment

Before writing a single sentence, gather the inputs. Do not skip this. A weak case study almost always traces back to a weak intake.

Step 0: Prerequisites

Check .agents/product-marketing-context.md — load ICP, positioning, messaging pillars. If missing, run cm-context first. The case study must reinforce a messaging pillar; otherwise it's an unmoored story.
Get raw interview material — recorded Zoom, transcript, support emails, NPS comments. Without primary quotes, the case study reads generic.
Get permission scope — full name + company + logo? Anonymized? Logo only? This determines what version you can ship.
Get the numbers — at minimum 2-3 quantified outcomes (time saved, cost saved, revenue gained, % improvement). No metrics = no case study, just a testimonial.

Read the full file on GitHub · 621 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 621 lines · 45 tokens per session scan A ad5c8b411ab5

Subscribe to this mod's changes

case-study is a skill published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 7,101 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Marketing and SEO Writing and docs

case-study next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
case-studyclassicchins/compounding-marketing	Skill	8	5mo ago	MIT	A	45	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code