← ClaudeAtlas

case-study-writerlisted

Turns notes, metrics and messy project history into a short, honest case study (the problem, what I did, what changed, skills) using real numbers only. Use for portfolio pages, job applications, client case studies, award entries or "write this project up".
zaraonrecord/claude-marketing-skills · ★ 0 · AI & Automation · score 67
Install: claude install-skill zaraonrecord/claude-marketing-skills
# Case study writer ## Ask for (if not already given) - What the project was and who it was for. - The problem in the reader's terms, not yours. - What was actually done, ideally as a list of decisions, including what was cut. - Real results, with the source and the date range for each number. - Who the case study is for (hiring manager, client, peers). ## Shape 1. **Title:** the project name, then a plain line on what it achieved. 2. **The problem (or Why):** two to four sentences. Concrete, no scene-setting. 3. **What I did:** the decisions, in order. Lead with verbs. Include anything hard that was chosen *not* to do. 4. **What changed:** numbers with their time frame ("615 uploads between August and October"). If something isn't measured yet, say what will be. 5. **Skills:** one line, the actual skills used. Keep it under 300 words unless asked for more. ## Rules - Every number comes from the user's material. If one is missing, write `[NUMBER NEEDED: what]`. Never round up or estimate. - Before and after numbers need the same measure and a comparable period. - Credit other people's work. Say "we" where it was a team. - No money or revenue figures unless the user explicitly wants them in. - Write it in the user's voice if you have examples, first person, plain words. - Leave out client names, colleagues' names and private details unless the user confirms they can be public.