Presentation blueprint

Skill Smirnov-Labs/claude-skills/skills/presentation-blueprint

Use when the user needs to create a presentation, pitch deck, slide deck, or visual summary about a project, codebase, website, or topic. Triggers on requests like 'build a deck', 'create a presentation', 'make slides about', or 'pitch deck for'.From its SKILL.md

Install

npx -y skills add Smirnov-Labs/claude-skills --skill presentation-blueprint

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, as published. Nobody here has run it

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific delegated task, do NOT follow this skill — skip it and return to the task you were given. </SUBAGENT-STOP>

Presentation Blueprint

Fortune 500 presentation consultant. Pipeline: analyze, strategize, outline, style, render.

Prerequisites

Verify document-skills:pptx is available. If missing, instruct user to install it and stop.

Presentation Types

Type	Triggers	Slides
Pitch	fundraise, investors, startup	10-12
Technical	architecture, system design, API	15-20
Update	status, quarterly, progress	5-8
General	summarize, overview, "about"	10-12

Pipeline

digraph { rankdir=LR; Analysis->Strategy->Outline->Style->Render; Outline->Strategy [label="reject\nmax 3"]; Outline [label="Outline\n(approval gate)"]; Style [label="Style\n(approval gate)"]; }

Phase 1: Source Analysis

Per ./source-analysis.md. Sources: codebase (README, docs, package.json, CLAUDE.md, git log), website (WebFetch: landing, about, pricing, features), user interview (3-5 questions). If a source fails, note and continue. Interview alone is minimum viable path.

Phase 2: Strategic Blueprint

Per ./narrative-frameworks.md. Define: objective, audience, key message, ask, narrative arc. Present Presentation Strategy to user for confirmation before proceeding.

Phase 3: Slide Outline

Format: Slide N: [Type] — "Key message". Approval gate: user must approve. Max 3 revision loops, then offer "start over" or "abort". Warn at 25+ slides.

Phase 4: Style Confirmation

Type	Default
Pitch	Dark, bold, high-contrast
Technical	Clean, structured, diagram-heavy
Update	Data-heavy, minimal decoration

Approval gate. Pass style label + parameters to pptx skill. No intermediate document.

Phase 5: Render & Review

Delegate to document-skills:pptx html2pptx workflow. Reference ./slide-archetypes.md for layouts. No speaker notes (async-first). No incremental updates — each invocation produces one complete deck. Rendering errors surfaced by pptx skill.

Guardrails

No fabricated data. Flag secrets to user.
Phase 3 + Phase 4 approval mandatory.
Max 25 slides. One deck per invocation.

Red Flags

Never	Why
Fabricate metrics	Destroys credibility
Skip approval gates	User loses control
Generate filler slides	Wastes attention
Include secrets/API keys	Security breach
Render before approval	Wrong output
Assume style without confirmation	Style mismatch