Wardn HubTrusted MCP server directory.

Registry

  • MCP Servers
  • Skills
  • Categories

Resources

  • API docs
  • Score method

Contribute

  • Submit server
  • Advertise
© 2026 Wardn Hub
Wardn Hub
MCP ServersSkillsCategoriesAPI docsSubmit server
Submit server
skills/mohitagw15856/pm-claude-skills/case-study-writeup

case-study-writeup

1
mohitagw15856/pm-claude-skills·Audit passed·Snapshot d4c12c4fc8b2
Installs
0

Summary

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.

SKILL.md

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").

BeforeAfter

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.

Related skills

capacity-planningcompetitor-teardowncontext-engineering-reviewrunbook-writerreceipts-audit