deck

Generate investor-ready pitch decks from BRIEF.md with Marp markdown and multi-critic review.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/rjwalters/anvil --skill deck-rjwalters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deck
Source: https://github.com/rjwalters/anvil/tree/main/anvil/skills/deck
Command: npx skills add https://github.com/rjwalters/anvil --skill deck-rjwalters

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Pitch decks are easy to write badly: they overflow visually, lack a coherent narrative, make unsupported market claims, and include traction/team numbers that can’t be defended during diligence.

Core Features & Use Cases

  • No-fabrication brief intake (deck-brief): converts founder-provided refs into a structured BRIEF.md so the drafter can’t invent numbers, names, logos, or assets.
  • Lifecycle deck production (deck-draft → deck-review → deck-revise): creates Marp slide source plus speaker notes, then scores problem clarity, traction/proof, and team credibility with a critical-flag gate.
  • Deck-specific multi-critic review: runs parallel critics for narrative arc, ask specificity, market math/differentiation, and design polish, then aggregates their findings into an advance/block verdict.
  • Rendered-artifact validation (deck-figures + deck-design + deck-vision): renders figures and deck.pdf, then checks rendered-only issues like overflow, label cropping, axis legibility, palette adherence, and mathtext artifacts.

Quick Start

Run the full lifecycle for a thread named acme-seed by executing deck-brief acme-seed, then deck-draft acme-seed, then deck-figures acme-seed, then deck-review acme-seed, and finally deck-revise acme-seed until the verdict advances.

Frequently Asked Questions about deck

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an investor pitch deck from markdown?

To generate an investor pitch deck, this Skill uses Marp markdown to create slide source plus speaker notes, then renders a deck.pdf with deterministic figures. It follows a structured drafting, rendering, and multi-critic review lifecycle to ensure the output is investor-ready.

How does the no-fabrication brief prevent unsupported claims in a pitch deck?

The no-fabrication brief converts founder-provided references into a structured BRIEF.md contract. This prevents the drafter from inventing numbers, names, logos, or assets, ensuring all traction and team claims can be defended during diligence.

What is the best way to review a pitch deck for narrative and market claims?

The best way to review a pitch deck is running parallel critics for narrative arc, ask specificity, market math, and design polish. The multi-critic review scores problem clarity, traction, and team credibility, then aggregates findings into an advance or block verdict.

How do I validate rendered PDF pitch decks for visual overflow and label cropping?

To validate rendered PDF pitch decks, this Skill checks rendered artifacts for overflow, label cropping, axis legibility, palette adherence, and mathtext artifacts. It renders deterministic figures and the final deck.pdf to catch design issues.

Can I use Marp to produce fundraising pitch decks with automated revision planning?

Yes, you can use Marp to produce fundraising pitch decks with automated revision planning. The lifecycle production creates Marp slide source, scores it with critical-flag logic, and generates revision plans across parallel critics until the verdict advances.

What are the limitations of using automated critics for pitch deck revision?

A limitation of using automated critics for pitch deck revision is that the process requires strict adherence to a no-fabrication BRIEF.md contract. The critics cannot validate claims outside the provided brief and rely on deterministic rendering to catch visual design issues.