agentsclimarketplace
Sign in

Case study writer

Skill styfinity/claude-marketing-department/skills/case-study-writer

Turns a real customer result into a structured case study — situation, sticking point, intervention, numbers, quotes — plus a short social version cut from the same material. Use when a genuine result exists and needs to work as proof across the funnel.From its SKILL.md

Install
npx -y skills add styfinity/claude-marketing-department --skill case-study-writer

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

  • 6 stars6 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

2.9 KB, as published. Nobody here has run it

Case Study Writer — proof, structured

A case study is not a testimonial with padding. It is the story of a decision the reader is about to make, told by someone one step ahead of them. The structure does the selling: a before-state the reader recognises as their own, a mechanism they can believe, and numbers they could check.

Inputs

  • The customer result and all raw material — notes, metrics, quotes, timeline: $ARGUMENTS
  • From marketing-brief.md if present: the ICP (so the story is framed for the right reader), the language bank, positioning & message, the banned-phrases list, and any rules on naming customers publicly.

Do this

  1. Inventory the raw material: who the customer is (and what may be named publicly), the before-state, what was actually done, the numbers with their timeframe, and verbatim quotes. List what is missing and ask once — none of it gets invented.
  2. Pressure-test the numbers. Baseline, timeframe, and what else was happening that could explain the change. A number without a baseline is a claim, not proof — present it honestly or leave it out.
  3. Write the case study in this shape:
    • Title — result-led and specific, no hype adjectives.
    • The situation — the before-state in the customer's words; the target reader should say "that's me" by line three.
    • The sticking point — what they had already tried and why it failed.
    • The intervention — what was done, step by step. The mechanism is the persuasive part; show the work.
    • The numbers — baseline to result, timeframe, context.
    • In their words — real quotes only, lightly trimmed, never improved.
    • What this means for you — the bridge to the reader, one CTA.
  4. Cut the social version: hook, three-beat arc, one number, CTA — reshaped for the feed, not compressed from the long copy.
  5. Run the naming pass. Apply the brief's rules on naming customers: keep the numbers, drop names where required, and note anything that needs the customer's sign-off before publishing.

Output

The full case study, the social version, and a proof-integrity note: the source of every number and quote, plus what to confirm with the customer before it ships.

Rules

  • Every number and quote traces to a real source. Nothing composite, nothing illustrative — if it is not real, there is nothing to write.
  • Curiosity belongs in the title, never in the numbers.
  • The intervention sells the method, not the vendor. Readers trust work they can see.
  • Keep the customer the hero. The company is the guide who turned up with a map.

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.