agentsclimarketplace
Sign in

Case study extractor

Skill nthnclrk/enablement-skills/skills/case-study-extractor

Extract credible customer stories, proof points, outcome claims, and approved quotes from notes, transcripts, and source data. Use when asked to turn customer evidence into an internal proof story, case-study draft, quote bank, or publication-ready evidence packet. Route cross-account pattern synthesis to field-feedback-synthesizer and final one-pager or slide packaging to one-pager-and-slide-outline.From its SKILL.md

Install
npx -y skills add nthnclrk/enablement-skills --skill case-study-extractor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.2 KB, as published. Nobody here has run it

Case study extractor

Permissioned proof. Evidence strength and permission to publish are different decisions.

If the metric has no baseline, it is not a result yet. If the quote is reconstructed from a summary, it is not a quote.

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.

Confirm Inputs First

Ask only for what changes claim strength or reuse:

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

Do not invent numbers, quotes, or approvals.

Read The Right Reference

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.

Default Workflow

  1. Set the boundary. Sources, audience, and reuse permissions before any narrative. Strength and permission stay separate.
  2. Extract units. Starting state, problem, intervention, adoption, result. Source IDs on each. Keep conflicts.
  3. Validate numbers. Definition, baseline, result, period, population, calculation, attribution limit. Opinion is not causality.
  4. Handle quotes exactly. Verbatim, with speaker, date, context, locator. Paraphrases stay outside quotation marks.
  5. Classify claims: Verified, Supported, Anecdotal, Unverified. Publication status is a different field.
  6. Tell the story only where the evidence links challenge, approach, and outcome. Keep the conditions that limit transfer.
  7. Produce the smallest requested branch: quote bank, proof-point packet, internal narrative, customer-review draft, or publication packet.

For cross-account patterns use field-feedback-synthesizer. For final packaging use one-pager-and-slide-outline.

Do not contact a customer, request approval, or publish without explicit user authorization.

Output Contract

Every branch includes use status, locators, permission fields, and the gaps that block the requested use.

  • Quote bank, proof-point packet, internal narrative, customer-review draft, or publication packet
  • Never the larger dossier when a narrower branch is enough

Quality Bar

  • Every material claim and quote has a locator.
  • Numbers include baseline, period, population, and attribution limit.
  • Quotes are exact. Paraphrases are labeled.
  • Unknown permission never reads as approved.
  • The internal version is useful to a seller and still safe for review.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.