- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill case-study-builder -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill case-study-builder -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill case-study-builder -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill case-study-builder -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/BrianRWagner/ai-marketing-claude-code-skills/tree/HEAD/case-study-builderDel publicador
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?"
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:
Outcome Extraction Protocol — enforced on Field 4:
If the user says "results were good" or "things improved," stop and ask:
"I need at least one number to make this credible. Pick one:
- Revenue change (e.g., 'closed 3 new clients worth $15K')
- Time saved (e.g., 'cut from 10 hours to 2 hours/week')
- Lead volume (e.g., 'went from 0 to 5 inbound leads/month')
- Rough estimate is fine — it doesn't have to be exact."
Do not draft until Field 4 has at least one number.
Before drafting, reason through:
Tier system for results language:
The client is the hero. You are the guide.
Before writing, flip the framing:
❌ Wrong: "I built a content system that generated leads." ✅ Right: "Sarah went from scrambling to fill her pipeline to getting 3 inbound inquiries per week — all from a content system we built in 6 weeks."
Every format should be written from what the CLIENT experienced, not what YOU delivered.
Formula: [What was done] + [scale/scope] + [for who] + [result or timeframe]
[Strong action verb] [what was delivered] for [specific client descriptor].
[Outcome metric] in [timeframe].
Example:
Built a full content system for a Series B SaaS founder with no marketing team. 0 to 3 inbound leads/week in 6 weeks.
Structure — 4 paragraphs, 150–250 words:
**Set the scene:** [Their situation when you arrived — 2-3 sentences with stakes]
**Show the complexity:** [What made this hard — 2-3 sentences]
**What happened:** [Specific actions taken — no feature lists, just moves]
**What changed:** [Outcome — the number + the transformation]
# Case Study: [Client Name or Descriptor]
## The Challenge
[2-3 paragraphs: situation, stakes, what wasn't working]
## The Approach
[Phases or steps — what happened and in what order]
## The Results
[Metrics, before/after comparison, named outcomes]
## Key Details
- Client: [Named or "A [descriptor] company"]
- Industry: [Sector]
- Timeline: [Duration]
- Scope: [What was delivered]
## What Made This Different
[Unique angle, unexpected obstacle, or pivotal insight]
## Client Quote
> "[Testimonial — or placeholder if not yet collected]"
> — [Name], [Title]
After generating all three formats, evaluate:
Two-liner:
Story version:
Full case study:
Flag any failure: "The story version has no tension — add one obstacle or unexpected challenge before the 'What happened' paragraph."
## Case Study: [Client Descriptor] — [Date]
### Situation Summary
[2-sentence analysis from Phase 1]
Result tier: [1/2/3/4]
---
### Format 1: Two-Liner
[Final copy]
### Format 2: Story Version
[Final copy]
### Format 3: Full Case Study
[Full markdown]
---
### Self-Critique Notes
- Two-liner: [pass/issue]
- Story: [pass/issue]
- Full: [pass/issue]
### Distribution Plan
[Where to use each]
### Next Step
[If no quote collected → run testimonial-collector]
[If strong story → suggest LinkedIn post from story format]
Cross-reference: If a client quote was captured here, run testimonial-collector to properly format and score it for your testimonial library.
Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com
Turn client wins into formatted case studies for proposals, social proof, and sales conversations. Use when someone needs to document results, build credibility, or create reusable proof assets.
---name: case-study-builderdescription: Turn client wins into formatted case studies for proposals, social proof, and sales conversations. Use when…---# case-study-builder/SKILL.mdPreguntas frecuentes
Descarga case-study-builder/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/BrianRWagner/ai-marketing-claude-code-skills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.