Claude Skill

case-study-writer

Turn client projects into commercial case studies - problem, solution, results, and metrics. Use to build sales proof from delivered work.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_case-study-writer-e9c73a3.zip · 1 KB

navinspire-ia/navin 31 4 forks AGPL-3.0 Updated 4d ago

Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/case-study-writer

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart

Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Case Study Writer

Overview

A case study sells when a prospect recognizes their own problem in it. Structure around the client's journey, not your features.

Structure

Snapshot box - client, sector, scope, 2-3 headline results
The challenge - their situation before, stakes, what they tried
Why us - selection criteria (as they'd tell it)
The solution - what was done, phased, with just enough technical depth
The results - numbers first (before → after), then qualitative wins, then a client quote
What's next - ongoing relationship (proves satisfaction)

Getting the material

Project docs, final reports, KPIs from delivery
Interview questions for the client/team: "what changed day-to-day?", "what number moved?", "what surprised you?"
If numbers are confidential: use percentages, ranges, or anonymize the client

Workflow

Pick the project with the clearest measurable outcome.
Gather material; draft the results section FIRST - no results, no case study.
Write the narrative; keep it 400-800 words for web, 1-2 pages for PDF.
Get client approval on the final text and logo usage - mandatory.
Produce formats: web page, PDF one-pager (pdf-generator), slide (pptx-generator), social snippets (content-recycler).

Rules

Real numbers, client-approved quotes - never embellish.
One case study per target segment beats ten generic ones.

Files (navin)

SKILL.md 1.6 KB

---
name: case-study-writer
description: Turn client projects into commercial case studies - problem, solution, results, and metrics. Use to build sales proof from delivered work.
metadata: {"navin":{"emoji":"🏆","category":"writing"}}
---

# Case Study Writer

## Overview

A case study sells when a prospect recognizes their own problem in it. Structure around the client's journey, not your features.

## Structure

1. **Snapshot box** - client, sector, scope, 2-3 headline results
2. **The challenge** - their situation before, stakes, what they tried
3. **Why us** - selection criteria (as they'd tell it)
4. **The solution** - what was done, phased, with just enough technical depth
5. **The results** - numbers first (before → after), then qualitative wins, then a client quote
6. **What's next** - ongoing relationship (proves satisfaction)

## Getting the material

- Project docs, final reports, KPIs from delivery
- Interview questions for the client/team: "what changed day-to-day?", "what number moved?", "what surprised you?"
- If numbers are confidential: use percentages, ranges, or anonymize the client

## Workflow

1. Pick the project with the clearest measurable outcome.
2. Gather material; draft the results section FIRST - no results, no case study.
3. Write the narrative; keep it 400-800 words for web, 1-2 pages for PDF.
4. Get client approval on the final text and logo usage - mandatory.
5. Produce formats: web page, PDF one-pager (`pdf-generator`), slide (`pptx-generator`), social snippets (`content-recycler`).

## Rules

- Real numbers, client-approved quotes - never embellish.
- One case study per target segment beats ten generic ones.