The case-study skill: turn one win into something you can send

You finished the thing. It works, the person is happy, and it's sitting in a folder doing nothing for you. Then someone asks what you've built and you send a screenshot, which tells them exactly nothing about whether it would work for them.

The same project, written up properly, is the thing you send to the next prospect. Where they started, what you built, what changed, and one honest line about the hard part. That last section is the one everybody cuts, and it's the one that makes the rest believable.

The case-study skill is one of the 55 free skills in our freeskills repo. It interviews you about one win, handles the numbers honestly, and writes two versions: a tight one for a DM and a longer one for a post or a portfolio. It works for a paid client, a free build, or your own project.

A skill is a folder of instructions that Claude Code loads as a slash command. Copy it into your skills directory and it's available everywhere.

Restart Claude Code or open a new session. That's the install finished. No API keys, no config.

Type /case-study. First it asks what kind of win this is, because a paid client, a free favor, and your own project each get written differently. A free build counts as proof, and the skill won't apologize for it or mention it was free unless you want that in there.

Then it interviews you one question at a time, and it pushes when your answers are short. What was it costing them before, what did you actually build, what's different now, is there a real number, what was the hardest part. Expect to be asked what changed twice if your first answer is soft. It saves the result to ~/case-studies/ with the five sections, both versions, and a note on what's measured versus described.

On numbers: it will not invent one, and it won't let you round a guess into a fact. If you give it a figure it can't trace to a source, it asks where it came from and downgrades it to a plain description if the answer is a guess. A concrete before and after with no number at all is genuinely strong, and the skill treats it that way.

Give it the raw story in whatever words come out. The interview will pull the rest.

The long one is for a portfolio. The short one is what you actually send when a prospect asks if you've done this before.

Naming a client without asking is the fastest way to lose one. Handle it in the same sitting.

What this skill actually does, in the time it takes to say it out loud.

1. 1Hook: there's a brand new free Claude skill that takes you from a finished project sitting in a folder to a short write-up you can send a prospect today.
2. 2Mechanism: you hand it one finished project. It interviews you one question at a time, and the one it pushes hardest on is what the situation was costing before you showed up. Then it checks every number against something you actually observed and turns anything you cannot source into a plain description instead. You get five short sections in two shapes: a tight version to send someone in a DM, and a longer version to post.
3. 3Transformation: when someone asks if you've done this before, you send one link instead of a screenshot and a paragraph of explaining.
4. 4Close: the write-up is free, one of 55 skills. If you want a steady run of projects worth writing up, Claude Code Club is 9 dollars a month. Link's below.

Tonight: install it, write up the last thing you built, and send the short version to one person who has the same problem your client had. One person is the whole task.