case-study-extraction

case-study-extraction is a skill for Claude Code, Codex from peterod99/consultant-skills. It costs 35 tokens per session (1,123 once invoked), scanned A, original, MIT.

A method for turning a completed client project into a case study: a short account of the problem, the work, and the measurable result.

In plain words
What is it for?
Use it to structure a client debrief and create a LinkedIn post or short document showing what changed and by how much.
Why use it?
It helps preserve useful project details while they are fresh instead of relying on vague claims about past work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to structure a client debrief and create a LinkedIn post or short document showing what changed and by how much.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/peterod99/consultant-skills/case-study-extraction
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 peterod99/consultant-skills --skill case-study-extraction
Clone the repo
git clone --depth 1 https://github.com/peterod99/consultant-skills

Made for: Claude Code, Codex.

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.

agentmods badge for case-study-extraction

README.md
[![agentmods](https://agentmods.dev/badge/skills/peterod99/consultant-skills/case-study-extraction/github.svg)](https://agentmods.dev/skills/peterod99/consultant-skills/case-study-extraction)
Your own site
<a href="https://agentmods.dev/skills/peterod99/consultant-skills/case-study-extraction"><img src="https://agentmods.dev/badge/skills/peterod99/consultant-skills/case-study-extraction/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.

agentmods 80×15 button for case-study-extraction

Your own site · 80×15
<a href="https://agentmods.dev/skills/peterod99/consultant-skills/case-study-extraction"><img src="https://agentmods.dev/badge/skills/peterod99/consultant-skills/case-study-extraction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,123 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.01123
Opus 5 $0.00017 $0.00562
Sonnet 5 $0.00007 $0.00225
Haiku 4.5 $0.00003 $0.00112

Measured 8d ago against content hash 2e30f075d440, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

case-study-extraction 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 8d 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.

case-study-extraction/SKILL.md · 39 lines

How it starts

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

Case Study Extraction

When to use

After a significant client project closes, extract a deployable proof asset before the engagement fades from memory. A case study is a 3–5 minute LinkedIn post or a 500-word document that converts prospects 3–5x better than generic positioning. Run this within 30 days of project completion while details are fresh and client is still celebrating wins.

The framework

  1. Schedule a debrief interview. Spend 30 minutes with your champion (the person who hired you) asking: What did they expect before you arrived? What changed? What surprised them? What would they tell a peer in the same situation? Record or take detailed notes.
  2. Extract the before/during/after arc. Before: their challenge, constraint, or gap (the status quo). During: your intervention and key decisions (the method: brief; don't oversell process). After: the measurable improvement in their terms (revenue, time, efficiency, risk reduction, staff retention, customer satisfaction).
  3. Quantify the result in their language, not yours. "Increased conversion rate by 23%" beats "implemented a new sales process." "Cut customer acquisition cost from $200 to $84" beats "optimized the funnel." Dollar figures, percentages, and time-saved metrics resonate; methodological descriptions do not.
  4. Write a 3–5 sentence narrative. Open with the problem (1 sentence). Middle: the intervention and why it worked (2 sentences). Close: the outcome and one insight or lesson (2 sentences). Keep it conversational, not marketing-speak.
  5. Add one insight or lesson. After describing the result, ask your client: What would you tell a peer facing the same challenge? Capture their unfiltered answer. That's the credibility knot: not your genius, but real client voice.
  6. Attach a proof metric. One number (revenue generated, time saved, percentage improvement, or staff impact) that proves the project mattered. Specificity beats roundness; $47k in new ARR generated beats "significant revenue impact."

Read the full file on GitHub · 39 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.

  1. 8d ago First seen · 39 lines · 35 tokens per session scan A 2e30f075d440

Subscribe to this mod's changes

case-study-extraction is a skill published in the GitHub repository peterod99/consultant-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,123 once invoked, about $0.0002 per session on Opus 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.

Related

Other skills, from other repositories

strategy-consulting-visualization

Use when turning any content into clear, professional visualizations - board slides, reports, proposals, research summaries, training materials, technical diagrams, infographics, process flows, timelines, benchmarks, waterfall charts, or data-backed visual specs for any audience.

kgraph57/mckinsey-style-visualization-skill · 58 tokens

mckinsey-market-research-deck

End-to-end playbook for producing a top-tier, McKinsey-style market-research deck (HTML page-turning presentation + print-ready PDF) for a brand or product category. Covers the research methodology (TAM/SAM/SOM bottom-up, Good/Better/Best framework, competitor profiling, customer pain points, unit economics, business…

norahe0304-art/30x-mckinsey-research-deck · 188 tokens

mckinsey-deck

Turn any content into a top-tier McKinsey-style deck — a 1280×720 page-turning HTML presentation that also prints to a clean per-slide PDF. Use when the user wants a "McKinsey-style deck / presentation", a polished slide deck or PDF from notes/content, an executive/board/investor deck, or to "make slides / a deck / a…

norahe0304-art/30x-mckinsey-research-deck · 119 tokens

setup

Interactive setup wizard that configures the GTM Engine for a new user. Collects company context, team info, ICP, personas, messaging, and signals, then generates all config and context files.

himanshusaleria/gtm-engine · 0 tokens

good-morning

Daily morning briefing that pulls calendar, tasks, pipeline, and outreach data into one view.

himanshusaleria/gtm-engine · 0 tokens

cold-email

Write cold outreach emails using signal-based, pain-first messaging. Improves itself over time.

himanshusaleria/gtm-engine · 21 tokens