Menu

Individual skill

b2b-case-study-production

0upvotes

Use this skill when proof assets need to be produced from real client work: "write a case study", "we need case studies for the new site", "our clients won't let us name them", "the sales team has nothing to send", "turn these client results into stories", "anonymize this client win", "build a case study section". Produces a case study series with an intake process, an anonymization framework that keeps stories credible without naming anyone, and a deployment map that puts each story in front of buyers in motion.

skills/vesselin-malev/b2b-case-study-production/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Applies when real client results exist and proof assets do not. Produces a series of case studies a skeptical buyer believes and a sales team actually sends.

## The job of a case study

A case study succeeds when a specific buyer recognizes their own situation in the first hundred words and finds the causality plausible all the way down. It is written for the skeptical read: a buyer who has been burned before, scanning for the seam where marketing took over from reality. Applause is a side effect. Recognition closes deals.

## Real numbers, few of them

One or two verifiable anchor numbers per story. Everything else is narrative: what changed operationally, who stopped doing what, which meeting got shorter. A page carpeted in metrics reads as invented even when every figure is real, because buyers know real engagements produce two clean numbers and a lot of texture. And the rule under the rule: never fabricate, never round up, never "roughly double" a 1.7x. One invented figure, discovered, poisons every honest story in the set.

## Anonymize without bleaching

Clients who refuse to be named still produce usable stories, and the disguise follows a strict trade: drop the identifiers, keep the texture. Describe the client by durable attributes, a size band, a specialty or vertical, a region, a situation, specific enough that a peer thinks "that is exactly us", general enough that a determined guesser cannot confirm the identity. The full attribute table, rounding rules, and the re-identification check are in `references/anonymization-rubric.md`. The mediocre version anonymizes by deleting everything interesting, leaving "a mid-sized company improved efficiency", which protects the client by making the story worthless.
Back to top