Case Study Testimonial Builder is a skill that takes raw client project data — notes, metrics, and quotes — and produces a structured “Case Study Pack” suitable for websites, sales decks, and social media. It accepts optional JSON source notes as input and outputs both Markdown for human readers and JSON for automated workflows or CMS imports, generating both formats simultaneously from a single run.

The skill applies evidence normalization, validating metrics and claims against the source data before including them in any output. It generates Value Hooks and Proof Snippets intended for use in emails and landing pages, and produces LinkedIn-ready snippets alongside multiple testimonial variants. A claims review step automatically flags unverified or sensitive claims so they can be reviewed for compliance or client approval before publication.

This is a developer-oriented, CLI-driven workflow rather than a freeform prompt. It is designed to enforce consistency across multiple output formats from a single evidence set, reducing the risk of inconsistent or unsupported claims appearing across different marketing materials. The skill acts as a bridge between project delivery artifacts and marketing output, giving teams a repeatable process rather than a one-off generation.

Use cases

Convert post-project delivery notes into a publishable case study in Markdown

Generate LinkedIn snippets and testimonial variants from a single set of client metrics

Produce JSON-formatted case study data for automated CMS import

Flag unverified claims before submitting marketing copy for client or compliance approval

Create Value Hooks and Proof Snippets for email campaigns and landing pages from existing project data

Normalize and validate metrics from raw project records before including them in sales materials

When to use it

When converting completed project data into structured, multi-format marketing assets

When consistency and evidence traceability across multiple output formats is required

When a claims review or compliance step is needed before publishing testimonials

When the team needs JSON output for CMS or automated marketing pipeline imports

When not to use it

When no source project data, metrics, or quotes are available to ground the output

When the required output format is not Markdown or JSON

When a free-form, interactive writing assistant is needed rather than a structured workflow

When there are no tools listed and a specific MCP server transport is required