agentleFS
Sign inStart free
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/case-study-writer/SKILL.md

case-study-writer

Skill1 starsChanged 23 days agoMITView on GitHub

Turns a completed engagement into a client-approved case study when you need proof of results to win similar work.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use after an engagement closes with measurable results and the client has agreed to be referenced, or when building a library of proof for …

    line 9
  2. Distinctive:

    Add a short line on who this is relevant for and a clear next step for the reader.

    line 24
  3. Distinctive:

    Every number traces to a named source and baseline

    line 30

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Case Study Writer

When to use it

Use after an engagement closes with measurable results and the client has agreed to be referenced, or when building a library of proof for a target segment.

What Claude needs

  • client-context.md for business background
  • Engagement brief, starting situation and baseline numbers
  • Deliverables, outcomes and dates
  • Client quotes and what the client has approved for publication
  • Target audience for the case study

Method

  1. Confirm what the client has approved: name, logo, figures, quotes, or anonymised only.
  2. Describe the starting problem in the client's own terms, including what it was costing them.
  3. Explain the approach as three to five key decisions or steps, not a list of activities.
  4. Quantify results against the baseline, stating the period and how each figure was measured.
  5. Choose one quote that names a result or a change in confidence, and mark it for client sign-off.
  6. Add a short line on who this is relevant for and a clear next step for the reader.

Output format

Provide a one-page case study with headline result, situation, approach, results table (metric, before, after, period, source), quote and call to action, plus a 60-word summary for proposals and social posts.

Quality checks

  • Every number traces to a named source and baseline
  • Nothing goes beyond what the client approved for publication
  • Credits other contributing factors fairly instead of claiming all of the result

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free