Case Studies

@di-atomic44 packages on opvs.ai
SkillBetacommunication#proof-assets#b2b-marketing
v0.1.2Updated 3 Nov 20265 installs1 video2 articles

Turn a finished client engagement into a publishable, client-approved, compliance-safe customer story. Owns the 6-part narrative arc, mandatory metric provenance (every number sourced), the compliance framing (REACH/CLP/biocides — no conferred-status claims), and a human-owned two-gate approval workflow (release BEFORE the interview; approval BEFORE publish) on a provisioned board. Composes copy-engine (sentences), voice-builder (customer register), explainer-illustrations (before/after diagrams), section-designer (library layout), and @spideriq/publish-skills (publish + PDF + gated form). Guidance-only: the agent's own LLM runs the workflow following SKILL.md + 7 recipes; state persists via the OPVS coordination skills. Multilingual EN/DE/HE/RU/RO/FR/ES, compliance-aware. Backed by 25 metric-bearing real exemplars + 2 operational templates + 20 learnings + 6 enforcement scripts.

I had real wins — ONYX, Pamit, GUNGUARD, VayaPin — and no repeatable way to turn one into a proof asset I could actually publish. Every attempt was a bespoke negotiation: which numbers can I say, who signs off, what happens when the client edits the headline after approving it. So the strongest evidence the agency owns stayed buried in meeting transcripts. case-studies is the fix, and it does nothing on its own — it decides and composes. It owns the shape of a customer story and the discipline around it: a 6-part arc a script checks for completeness, metric provenance a script checks number by number, compliance framing that never claims a status a regulator confers, and a human-owned approval gate the skill reads but can never write. copy-engine writes the sentences, voice-builder carries the customer's register, explainer-illustrations plans the before/after diagrams, section-designer lays out the library, and @spideriq/publish-skills ships it — page, PDF, and gated form. Two rounds of research taught it the non-obvious parts. Secure the legal release before the interview, not after the draft, or a story dies at month six with all the cost sunk. Include the bumps, because a case study that reads as frictionless reads as fake. And never invent a baseline you didn't measure — the honest answer is sometimes "we can't publish a result for this one; here's what to instrument going forward." Backed by 25 real, sourced exemplars, two ask-and-release templates, 20 learnings, and 6 scripts that print PASS/FAIL with numbers the agent can't fudge.

Case StudiesFree · Claude, Codex, Antigravity

Features5

01A 6-part arc a script enforces

Situation, Challenge, Intervention, Result, Lessons, CTA — plus the two beats everyone drops: what they tried before, and the bumps along the way. A frictionless story reads as fabricated.

02Every number carries its source

No claim ships without an inline cite, and a percentage over 100% must show its baseline. 'Leads up 1,200%' fails; 'up 1,200% (3 → 39/month)' passes — and reads more honest.

03The client approves before you publish

Release is secured BEFORE the interview; two sign-offs (internal, then customer) before publish. The skill reads that gate — it never writes its own approval.

04It never claims a status it can't confer

For regulated work it writes 'supported the REACH dossier', never 'made them compliant'. Absolutes lose their footing inside a document full of measured claims.

05One story, many renders

The deep page for skeptical buyers, the one-sheet for the sales team, the ad cut for social. Publishing once is the single biggest waste — atomize from the start.

Videos1 video

Demo

Case Studies · Demo video

Demo · SpiderMedia

Articles about Case Studies2 articles

More like this

Shares a tag or category

More from @di-atomic

43 packages