What is case-study-extractor?

A tool for turning one sales-call recording, transcript, or set of notes into specific coaching advice. It focuses on observable changes for the next comparable call.

Use it to review discovery calls, product demonstrations, objection handling, technical checks, or closing conversations and choose one to three next-practice actions.

It avoids vague feedback that could apply to any salesperson and makes sure coaching is based only on evidence that was actually available.

case-study-extractor — Skill for Codex by nthnclrk/enablement-skills

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 nthnclrk/enablement-skills --skill case-study-extractor

Clone the repo

git clone --depth 1 https://github.com/nthnclrk/enablement-skills

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/case-study-extractor/github.svg)](https://agentmods.dev/skills/nthnclrk/enablement-skills/case-study-extractor)

Your own site

<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/case-study-extractor"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/case-study-extractor/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/nthnclrk/enablement-skills/case-study-extractor"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/case-study-extractor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 716 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.00082	$0.00716
Opus 5.5	$0.00033	$0.00286
Sonnet 5.5	$0.00016	$0.00143
Haiku 4.5	$0.00008	$0.00072

Measured 24d ago against content hash c9b3ac2b0b1b, 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-extractor 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 24d 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-extractor/SKILL.md · 65 lines

How it starts

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

Case study extractor

Extract customer evidence that a seller or writer can reuse with its limits and permissions intact.

A measured current value can be reported with its definition, period, and population. A change claim also needs a comparable baseline. Reconstructed statements are paraphrases, not quotes.

Honest. "In a three-customer pilot, unresolved handoffs fell 28% in 60 days. Directional. Not a benchmark. Named use requires customer approval we do not have."

Overclaim. "Customers cut delivery delays by 28% with MosaicOps."

Default to internal. Mark every external-use field Not approved or Unknown until you have the permission.

Inputs

Ask only for what changes claim strength or reuse:

Intended output and audience
Source packet with locators
Metric definition, baseline, period, population
Permission for name, logo, each quote, each metric, channel, and expiry

Do not invent numbers, quotes, or approvals.

Supporting material

Read references/case-study-template.md for claim statuses, the permission matrix, and story shape. Skip it if you are only extracting a quote bank.

Procedure

Set the boundary. Sources, audience, and reuse permissions before any narrative. Strength and permission stay separate.
Extract units. Starting state, problem, intervention, adoption, result. Source IDs on each. Keep conflicts.
Validate numbers. Check definition, result, period, population, and calculation. Require a comparable baseline for improvement claims, and check what else changed before attributing the result to the intervention. Retain credible qualitative evidence when no defensible metric exists.
Handle quotes exactly. Verbatim, with speaker, date, context, locator. Paraphrases stay outside quotation marks.
Classify claims: Verified, Supported, Anecdotal, Unverified. Publication status is a different field.
Tell the story only where the evidence links challenge, approach, and outcome. Keep the conditions that limit transfer.
Produce the smallest requested branch: quote bank, proof-point packet, internal narrative, customer-review draft, or publication packet.

Read the full file on GitHub · 65 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

24d ago Changed c9b3ac2b0b1b
2mo ago First seen · 65 lines · 82 tokens per session scan A e16ebb5ff4dc

Subscribe to this mod's changes

case-study-extractor is a skill published in the GitHub repository nthnclrk/enablement-skills (16 stars, last pushed 25d ago), licensed MIT. It adds 82 tokens to every session and 716 once invoked, about $0.0003 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-30.

Marketing and SEO

case-study-extractor next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
case-study-extractornthnclrk/enablement-skills	Skill	16	25d ago	MIT	A	82	Codex
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