case-study-writeup
Write a client case study that sells future work — challenge, approach, results. Use when asked to write a case study, a client success story, a pro…
它会碰到什么
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
Case Study Write-up Skill
A case study is your most persuasive sales asset — proof that you've solved this kind of problem before.
Weak ones narrate activities; strong ones lead with a result, show the before→after, and make the reader
(a future client) think "that's my problem too." This skill writes that — challenge → approach → quantified
outcome — ready for the themed PDF export or a portfolio page.
Required Inputs
Ask for these only if they aren't already provided:
- The client & context — who (or an anonymised descriptor — "a Series B fintech"), and their situation.
- The challenge — the problem you were brought in to solve, and what was at stake.
- What you did — your approach and the key moves (your contribution, specifically).
- The results — outcomes with numbers (before → after); a client quote if you have one.
Output Format
Case Study: [outcome headline]
Headline — lead with the result, not the client ("Cut onboarding time 60% for a Series B fintech" — not "Acme Engagement"). It's the hook.
1. The client & challenge — who they are and the problem, framed so a similar prospect recognises themselves. The stakes (what it was costing them).
2. The approach — what you did and why — enough to show expertise and judgement, not a play-by-play. Highlight the insight or decision that mattered.
3. The results — quantified outcomes, before → after. Lead with the headline metric; add supporting ones. If numbers are confidential, use ranges ("~40% faster").
| Before | After |
|---|---|
4. Client quote — a slot for a testimonial (with name/title/company if permitted) — third-party validation is the most persuasive line.
5. The takeaway — one line on the transferable lesson / what this proves you can do — pointing the reader toward their own version of the problem.
Note (for the user): get client sign-off before publishing; anonymise where needed; lead every section with outcome over activity.
Quality Checks
- [ ] The headline is the result, not the project/client name
- [ ] The challenge is framed so a similar prospect sees themselves in it
- [ ] Results are quantified (before → after), with ranges if confidential
- [ ] Your specific contribution is clear (not just "the team")
- [ ] Includes a client-quote slot for third-party proof
- [ ] Ends with a transferable takeaway that invites the next client
Anti-Patterns
- [ ] Do not title it after the client/engagement — lead with the outcome; that's what pulls the reader in
- [ ] Do not narrate activities without results — "we ran workshops" proves nothing; show what changed
- [ ] Do not bury or omit the numbers — quantified outcomes are the whole point; use ranges if you must anonymise
- [ ] Do not publish without client consent — confirm sign-off and anonymisation first
- [ ] Do not blur your role into the team's — a prospect is hiring you; show what you did
Based On
Case-study / social-proof marketing practice — result-led headline, challenge–approach–outcome, quantified before→after.
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
它属于哪个仓库
plugins/pm-consulting/skills/case-study-writeup/SKILL.md同一个仓库里的其他技能
同名技能的其他版本
有 3 个不同仓库或目录里都有叫 case-study-writeup 的技能。它们内容并不相同,别混用:
- mohitagw15856/pm-claude-skills — Write a client case study that sells future work — challenge, approach, results. Use when
- mohitagw15856/pm-claude-skills — Write a client case study that sells future work — challenge, approach, results. Use when