AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Case Study Builder

skill-rfstudioco-agentic-growth-team-case-study-builder · by rfstudioco

Run an end-to-end case study pipeline — interview questions → story extraction → publish-ready case study with metrics and quotes. Use when the user says "write a case study", "turn this customer into a case study", "interview customer X for a story", or is building proof assets.

— No reviews yet
0 installs
39 views
0.0% view→install

Install

$ agentstack add skill-rfstudioco-agentic-growth-team-case-study-builder

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-rfstudioco-agentic-growth-team-case-study-builder)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Case Study Builder? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Case Study Builder (Referral Squad)

Converts a happy customer into a published case study without the usual fluff. Opinionated format.

Triggers

  • "write a case study"
  • "turn customer X into a case study"
  • "interview our customer for a story"
  • "proof asset for "

Inputs required

  1. Customer name + contact
  2. What they bought / how they use the product
  3. Rough outcome — any metrics they've shared (even anecdotal)
  4. Interview transcript OR permission to generate interview questions first
  5. Target audience — which ICP segment is this case study for

Process

Step 1 — Pre-interview: generate the interview guide

If no transcript yet, produce a 30-minute interview guide following this spine:

  1. Before — what was life like before our product? (pain)
  2. Trigger — what made you start looking? (event)
  3. Evaluation — what did you consider? (alternatives)
  4. Adoption — how did you roll it out? (process)
  5. Outcome — what changed? (result — push for numbers)
  6. Future — what's next? (aspiration)

Include specific follow-up prompts under each:

  • "Can you quantify that?"
  • "What would have happened if you hadn't solved this?"
  • "What's a concrete moment that sticks out?"

Step 2 — Post-interview: extract the story

From the transcript, pull:

  • 3 numbers — real metrics with context (e.g., "cut onboarding from 2 weeks to 3 days")
  • 3 quotes — verbatim, emotional, specific (no "it's been a game-changer")
  • 1 scene — a concrete moment that anchors the whole story
  • 1 risk — what they were afraid of that didn't happen

If you can't find all of these, the case study isn't ready — flag it and suggest a second interview.

Step 3 — Draft the case study

Use this opinionated structure:

Headline          — outcome-focused, specific number if possible
Subhead           — who they are, one line
The problem       — 2 paragraphs, pain + trigger
The alternative   — what they tried before or considered
The solution      — how they use the product (specific workflow)
The results       — 3 numbers, in a row, with context
Quote             — their strongest pull quote, big and pulled out
What's next       — 1 paragraph, forward-looking
CTA               — "book a demo / start free / talk to sales"

Rules:

  • Lead with outcome, not "meet "
  • Avoid corporate-speak ("leverage", "synergy", "empower")
  • One quote per section max
  • Always link to ICP — "if you're a , this is you"

Step 4 — Approval loop

Produce a draft + a bulleted list of:

  • Facts to confirm
  • Quotes to approve verbatim
  • Numbers that need written permission

Send to customer for review before publishing.

Step 5 — Package for distribution

Produce three versions:

  • Long — web page (markdown / HTML)
  • Short — 500 words for email + PDF
  • Snippets — 3 pull quotes + 3 numbers formatted for paid ads (hand to Paid Ads Generator)

Output artifacts

  • case-study-.md (long)
  • case-study--short.md (email / PDF)
  • case-study--snippets.md (ads, landing page, social)

Handoff

  • Snippets → Paid Ads Generator + Landing Page Optimizer
  • Customer outreach → Advocate Identifier (are they open to reference calls?)
  • Published → Performance Reporter (track the asset's impact)

Example call

> "Write a case study on Acme Co. They moved from Salesforce to us 6 months ago. Champion is Jane, VP Sales. I have a 45-min call transcript attached. Target audience: mid-market RevOps leaders."

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.