designing-presentations

Design slide deck content from audience brief through critiqued storyboard into a structured markdown deck.md.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/pgoell/pgoell-claude-tools --skill designing-presentations-pgoell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: designing-presentations
Source: https://github.com/pgoell/pgoell-claude-tools/tree/main/plugins/presentations/skills/designing-presentations
Command: npx skills add https://github.com/pgoell/pgoell-claude-tools --skill designing-presentations-pgoell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Planning a presentation's storyline, message architecture, and per-slide content is often skipped or done ad hoc, leading to decks with weak arguments, topic-noun headlines, and unclear asks. This Skill provides a disciplined five-phase workflow that produces a complete, critiqued deck content plan before any slide is rendered. ## Core Features & Use Cases - Five-phase content design pipeline: Runs intake (audience brief), message architecture (SCQA and answer-first pyramid), storyboard, per-slide drafts with YAML front-matter, and a critique panel, writing one artifact file per phase. - Audit mode for existing decks: Consumes an existing deck.md and runs a deterministic heuristic audit plus three critic personas (audience, argument, visual) that return severity-tagged findings. - Resumable state tracking: File presence determines phase completion, so interrupted runs resume at the next phase without redoing finished work. - Use Case: A product manager needs a 20-minute executive briefing to get budget approved. The Skill interviews for audience and governing idea, builds the argument pyramid, storyboards 8-12 slides with sentence headlines, drafts each slide's YAML brief with speaker notes, and runs a critique panel before handoff to a rendering skill. ## Quick Start Ask the assistant to design the content of a 20-minute executive briefing deck for your topic, starting from the audience intake questions.

Frequently Asked Questions about designing-presentations

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

FAQPage Schema
How do I plan a presentation storyline before making slides?

Run the five-phase workflow: capture an audience brief, build an SCQA and answer-first pyramid message architecture, storyboard slides with sentence headlines, draft per-slide YAML briefs, then run a critique panel. The output is a single deck.md file ready for rendering.

How to audit an existing slide deck outline for weak content?

Provide a path to an existing deck.md to trigger audit mode, which runs a deterministic heuristic checklist covering sentence headlines, sourced evidence, specific decision asks, single-comparison charts, and slide-count bands. Three critic personas then review audience fit, argument logic, and visual clarity.

What output format does the presentation design workflow produce?

The workflow produces markdown only: five artifact files (audience-brief.md, message-architecture.md, storyboard.md, deck.md, audit-report.md). The deck.md uses per-slide YAML front-matter with slide_type, headline, visual, speaker_notes, and optional sources keys.

Can I resume an interrupted presentation design session?

Yes. Phase completion is determined by whether each artifact file exists and is non-empty, so re-invoking the skill scans the working directory and offers to resume at the next phase or restart an earlier one. Restarting an earlier phase invalidates later artifacts rather than silently overwriting them.

What are the limitations of the deck content audit mode?

Audit mode is markdown-only and cannot import PowerPoint, Keynote, or Google Slides files; content must be converted to deck.md first. Decks lacking the YAML schema get an advisory heuristic audit only, without the critic personas, and visual rendering issues are out of scope.