case-study-writer
Skill6 starsChanged 4 months agoMITView on GitHub
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.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- jqaisystems/jqai-ai-skillstheir own version, first seen Nov 1, 2026
- Nomanriaz786/claude-consulting-teamtheir own version, first seen Nov 1, 2026
- prosyo-ai/gtm-skilltheir own version, first seen Oct 25, 2026
- ghazanfar111212/claude-skills-performance-marketingtheir own version, first seen Oct 11, 2026
- aditya-ariosity/ux-ui-skillstheir own version, first seen Sep 2, 2026
- Gonadotrophic-tangent41/ux-ui-skillstheir own version, first seen Aug 9, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- whyashthakker/agent-skills-marketing★ 15same name
- prosyo-ai/gtm-skill★ 13same name
- jqaisystems/jqai-ai-skills★ 3same name
- aditya-ariosity/ux-ui-skills★ 2same name
- Nomanriaz786/claude-consulting-team★ 1same name
- ghazanfar111212/claude-skills-performance-marketing★ 0same name
- Gonadotrophic-tangent41/ux-ui-skills★ 0same name
- tjrice42/design-judgment-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- ad-scriptsSkill
- battlecardSkill
- brand-voiceSkill
- campaign-debriefSkill
- channel-pickerSkill
- cmoSkill
- competitor-teardownSkill
- content-calendarSkill
- creative-briefSkill
- customer-deep-diveSkill
- email-sequenceSkill
- experiment-backlogSkill
- funnel-mapSkill
- hook-factorySkill
- kpi-treeSkill
- landing-pageSkill
- launch-planSkill
- lead-magnet-builderSkill
- marketing-auditSkill
- market-research-sprintSkill
- message-mapSkill
- objection-mapSkill
- offer-builderSkill
- onboardSkill
- positioning-workshopSkill
- pricing-testSkill
- repurposeSkill
- research-to-briefSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Every number and quote traces to a real source.
- Distinctive: line 36
Keep the customer the hero.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.mdif 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
- 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.
- 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.
- 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.
- Cut the social version: hook, three-beat arc, one number, CTA — reshaped for the feed, not compressed from the long copy.
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

