skills/case-study-writeup/SKILL.md
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 project write-up, or a portfolio case for consulting/agency work. Produces a results-led case study — the client & challenge, your approach, quantified outcomes, a client quote slot, and a takeaway — structured to win the next client. Ready to export as a designed PDF.
npx skillsauth add mohitagw15856/pm-claude-skills case-study-writeupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Ask for these only if they aren't already provided:
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.
Case-study / social-proof marketing practice — result-led headline, challenge–approach–outcome, quantified before→after.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.