Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brianrwagner/case-study-builder
Turn client wins into formatted case studies for proposals, social proof, and sales conversations.
Passed 14 of 22 test cases with the skill, and 8 of 22 without it.
and 11 more in the full report
9 fixed5 passed either way5 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need a case study for a client project. We redesigned the customer portal for an e-commerce brand. The client was super happy, the UI looks much cleaner, and customer feedback has been overwhelmingly positive. Client name: ShopNova. Named allowed. Quote: 'Loved working with them.' Timeline: 6 weeks. Scope: UI redesign. Use case: website. Can you draft the proposal blurb and case study?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies that quantitative metric data is missing and requests at least one specific number from the user. | Missed | Passed |
| Refuses to output the drafted case study assets before receiving outcome metrics. | Missed | Passed |
The instructions your model reads when the skill loads.
Everyone wants social proof. Nobody makes time to create it. You finish a project, the client's happy, you move on — and six months later you're in a sales call with nothing to show.
This skill fixes that. Give me the raw details. I'll produce three formats you can use immediately.
Detect from context or ask: "Quick writeup, full case study, or full asset package?"
| Mode | What you get | Best for |
|---|---|---|
quick | 1 format: paragraph summary for proposals | Fast social proof, proposal inserts |
standard | 3 formats: proposal blurb, social proof pull-quote, sales story | Active pitching, LinkedIn, website |
deep | 3 formats + blog-ready case study + FAQ variant + campaign assets | Content marketing, SEO, sales enablement |
Default: standard — use quick if they say "just need something fast." Use deep if they want to turn the win into a marketing asset.
Before generating anything, collect all 8 fields:
| Field | What to Collect |
|---|---|
| 1. Client | Industry, company size/stage, named or anonymized? |
| 2. Before | What was broken or painful? Any numbers? |
| 3. Actions | What did you specifically do? Scope, timeline, role |
| 4. After | REQUIRED: at least one specific number |
| 5. Timeline | How long to achieve the result? |
| 6. Quote | Direct client quote if available |
| 7. Naming | Can we name the client, or must we anonymize? |
| 8. Use case | Where will this be used? (proposals / website / LinkedIn) |
Outcome Extraction Protocol — enforced on Field 4:
If the user says "results were good" or "things improved," stop and ask:
test cases passed, vs 8 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.