본문으로 건너뛰기
cccskills
무료GitHub에 공개

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.7 KB

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.

Example Trigger Phrases

  • "Write a case study."
  • "Turn this project into a client success story."
  • "Write up this engagement for our portfolio."
  • "Show the results we got for this client."

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 19일 업데이트

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 19일 업데이트

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 19일 업데이트

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 19일 업데이트

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 19일 업데이트

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 19일 업데이트

mohitagw15856의 스킬 모두 보기

이 스킬의 문제 신고