presentation-creator skill
✓ VerifiedBuilds end-to-end slide decks including story spines, visual systems, slide copy, and speaker notes in formats like Marp, Slidev, or reveal.js.
- GitHub stars
- 194
- Files
- 10
- Last commit
- Nov 10, 2026
- License
- MIT
- Allowed tools
- —
What does the presentation-creator skill do?
presentation-creator builds end-to-end slide decks including story spines, visual systems, slide copy, and speaker notes in formats like Marp, Slidev, or reveal.js.
Summary generated from the skill's SKILL.md.
About the presentation-creator skill
Creating structured, narrative-driven slide decks is what this skill enables for presenters and founders. It manages the entire production lifecycle, starting with a story spine and ending with a fully formatted deck. An agent should load this tool when a user needs to build a pitch deck, turn a document into slides, or design a presentation for a live talk or recorded session.
The process follows a strict eight-step workflow that includes gathering audience context, writing a narrative arc, designing visual systems, and drafting speaker notes. It produces output in Marp markdown by default, but can also generate Slidev, reveal.js, or Next.js web app decks. While it handles the content and structure, it does not create .pptx files directly; instead, it provides the outline and copy to be used by a dedicated PowerPoint skill. The tool ensures quality through a final QA pass that checks for contrast ratios, layout variety, and the three-second glance test.
What an agent can do with it
- 1Convert documents into slidesTransform a long-form document into a structured presentation with a clear story spine.
- 2Generate web-based presentation appsProduce a Next.js deck app designed for live demos or hosting at a specific URL.
- 3Design visual systems for decksEstablish color palettes and typography scales based on whether the venue is a dark hall or a bright room.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the presentation-creator skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the presentation-creator skill in Claude Code
~/.claude/skills/presentation-creator/SKILL.md
$ npx degit mblode/agent-skills/skills/presentation-creator ~/.claude/skills/presentation-creatorInstall the presentation-creator skill in Claude Code (project)
.claude/skills/presentation-creator/SKILL.md
$ npx degit mblode/agent-skills/skills/presentation-creator .claude/skills/presentation-creatorInstall the presentation-creator skill in Codex
~/.agents/skills/presentation-creator/SKILL.md
$ npx degit mblode/agent-skills/skills/presentation-creator ~/.agents/skills/presentation-creatorInstall the presentation-creator skill in Gemini CLI
~/.gemini/skills/presentation-creator/SKILL.md
$ npx degit mblode/agent-skills/skills/presentation-creator ~/.gemini/skills/presentation-creatorInstall the presentation-creator skill in Claude.ai
npx degit mblode/agent-skills/skills/presentation-creator presentation-creator && zip -r presentation-creator.zip presentation-creator # claude.ai → Customize → Skills → + → Create skill → Upload a skill → presentation-creator.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablemblode/agent-skills/skills/presentation-creator is public and reachablegithub.com/mblode/agent-skills/tree/HEAD/skills/presentation ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-10github.com/mblode/agent-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/mblode/agent-skills/blob/HEAD/skills/presentation ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/mblode/agent-skills/blob/HEAD/skills/presentation ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 108 linesgithub.com/mblode/agent-skills/blob/HEAD/skills/presentation ↗Pass
SKILL.md
View on GitHubPresentation Creator
Bold, minimal slide decks with a story underneath: spine to final QA.
- IS: slide decks end to end: story spine, slide sequence, slide copy, visual system, speaker notes, investor pitch decks, and decks built as a web app; output as Marp markdown (default), Slidev or reveal.js markdown, or a Next.js deck app.
- IS NOT: producing or editing the
.pptx/.potxfile itself (available presentation/PPTX skill or tool; hand it the finished outline, copy, and notes from this skill), charts inside a slide (externaldatavizwhere installed), long-form prose, marketing copy, or a spoken talk script outside slides (ghostwriter), or product UI (ui-design).
Workflow
Track this checklist:
Presentation progress:
- [ ] Step 1: Gather context (audience, setting, venue, three messages, output format)
- [ ] Step 2: Write the story spine and the ending (references/story-structure.md)
- [ ] Step 3: Outline the slide sequence (references/outline-structure.md)
- [ ] Step 4: Write slide copy (references/writing-slides.md; pitch decks: references/pitch-decks.md instead)
- [ ] Step 5: Design colour, type, and layout (references/visual-design.md)
- [ ] Step 6: Write speaker notes (references/speaker-notes.md); skip for a deck sent without a presenter
- [ ] Step 7: Emit the deck in the chosen format (references/output-formats.md or references/web-deck.md)
- [ ] Step 8: QA pass, output the slide-by-slide review table
Step 1: Gather context
Establish these, asking only for what the brief does not answer:
- Audience: internal (shared context, be direct) vs. external (build credibility, define terms).
- Setting: live talk, recorded/async, or a pitch deck sent to investors and read without you.
- Venue: a dark room or a large hall takes the dark system; a bright meeting room, daylight, or a deck that doubles as a handout takes a light palette. Ask when unknown, because it decides Step 5.
- The three messages: what the audience must remember after the deck.
- Output format: Marp markdown unless there is a reason otherwise. A web app when the deck should run a live demo or live at a URL. A
.pptxwhen the user names the file or a house template, produced by the externalpptxskill from this skill's outline, copy, and notes. Decide now, not at Step 7: the format sets the type and notes mechanics in Steps 5 and 6.
Route by setting:
- Live talk, internal, or recorded deck → Steps 2-8 in order.
- Investor pitch deck sent to be read → references/pitch-decks.md first. Its 10-slide framework replaces Step 3's outline, and its async copy rules replace
writing-slides.mdat Step 4 (do not load both: their density rules contradict). Step 2 still applies in compressed form; the spine is what stops a pitch reading as a feature list. Skip Step 6. The same company pitching live on a demo-day stage is a presented deck: use the standard path with the pitch framework as its outline.
Steps 2-7: Build the deck
Read each step's reference when you reach it:
| Step | Reference | Covers |
|---|---|---|
| 2. Story | references/story-structure.md | The spine template, writing the ending first, taking a position, stakes, the unstick move |
| 3. Outline | references/outline-structure.md | Narrative flow, 12 slide types, section colours, outline output format |
| 4. Write | references/writing-slides.md, replaced by references/pitch-decks.md on the pitch path | Headline patterns, body rules, copy per slide type, before/after examples |
| 5. Design | references/visual-design.md | Two colour systems, contrast thresholds, fluid and fixed type scales, layout patterns, slide type to layout mapping |
| 6. Notes | references/speaker-notes.md | Per-slide note structure, delivery cues, notes by slide type |
| 7. Emit | references/output-formats.md | Marp syntax and export, Slidev and reveal.js equivalents, the pptx handoff, where notes live in each |
| 7. Emit (web) | references/web-deck.md | Route-per-slide structure, navigation, layout primitives, motion, live demos |
| Changing this skill | evals/evals.json |
Behavioural scenarios with assertions. Never loads during a user task |
Read web-deck.md only after the copy exists. Primitives designed before the outline get shaped around slide 3 and fight every slide after it.
Step 8: QA pass (produces evidence)
Render the delivered format and inspect every slide. Record layout defects and measured contrast; a self-assigned glance score is editorial judgement. Keep the detailed table with the artifact when useful, and summarize material results in chat:
| # | Slide | 3-sec test | One message | Spine beat | Layout | Colour | Contrast |
|---|-------|-----------|-------------|------------|--------|--------|----------|
| 1 | Title | pass | pass | once upon a time | full statement | teal | 12.6:1 |
- 3-sec test: parseable in three seconds at arm's length (Duarte's glance test). Cut copy on any failure until it passes. Pitch decks are read, not glanced: substitute "makes sense forwarded with no context".
- One message: exactly one idea per slide; split slides carrying two.
- Spine beat: which beat of the Step 2 spine this slide serves. A slide serving none is a fact you found interesting; cut it.
- Layout: the layout should change when the slide's job changes. Flag a run of three or more identical layouts and keep it only when the section is deliberately a list.
- Colour: the section accent, or the full-bleed palette, matching what Step 5 assigned.
- Contrast: the smallest text on the slide against its background. 4.5:1 for body and captions, 3:1 only for text at 24px (18pt) or larger. Record the ratio, not "ok".
Deck-level checks below the table:
- Every spine beat has at least one slide, and the ending matches the one written first
- The deck states a position a reasonable person could disagree with
- One colour system throughout: accents per section, or full-bleed palettes, never both
- Recap slide has exactly one line per core section
- Speaker notes sit where the output format reads them (Marp and Slidev: an HTML comment at the end of the slide; reveal.js: a
Note:line;.pptx: the notes pane) - Pitch decks only: 10 slides plus an appendix at most, explicit ask slide (amount and use of funds), headlines pass the forwardable test
Fix observed defects and inspect affected slides again. If rendering is unavailable, label visual verification unrun.
Gotchas
- Dark deck in a bright room: the default dark system relies on the room. Under daylight or a weak projector the black background goes grey and white body text washes out. Ask about the venue in Step 1; take the light "paper" palette or a white background when the answer is bright, and test on the projector, not the laptop.
- Contrast checked at headline size only: a saturated full-bleed pair that reads at 100px fails at 20px caption size. Measure the smallest text on the slide from the actual hex values against the Step 8 thresholds.
- Export "PPTX" from Marp or Slidev and call it done: both rasterise each slide into an image inside the
.pptx. Text is not selectable or editable, so the deck the client wanted to edit is a stack of pictures. When editable PowerPoint is the deliverable, route to thepptxskill. - Notes and directives both live in HTML comments in Marp:
<!-- _class: lead -->is a directive,<!-- Open with the outage story -->is a presenter note. A note that starts with akey: valueline silently becomes a directive. - Fixed pixel type on a web deck: a deck sized for the presenter's laptop is a different deck on the projector and unreadable on the phone it gets forwarded to. Size in
clamp(); Marp and.pptxdecks are fixed canvases and take pt sizes instead. - Presented-deck density on a pitch deck sent by email: a 3-words-per-slide deck forwarded with no presenter is unreadable. Route to
pitch-decks.mdat Step 1, not after the deck is built. The inverse also fails: a 60-word slide on a demo-day stage. - Skipping the spine: jumping straight to slides produces a list of facts with no arc, then a rewrite once the missing narrative shows. Spine and ending first.
- Speaker notes as a script: a verbatim script gets read aloud and sounds flat. Notes are prompts: key point, talk-track bullets, transition line.
- Accents outside the section system: section colours are wayfinding; a random mid-section accent reads as a topic change that never happened. On a full-bleed deck the slide is the accent; the colour changes at the slide boundary, not inside it.
- Paragraphs on slides: the audience reads instead of listening and the speaker becomes redundant. Cut until the 3-second test passes.
Related skills
- External
pptxskill (anthropics/skills) where installed: creating, editing, and QA of the.pptxfile. This skill owns story, outline, copy, and notes; on a visual conflict inside a.pptx, this skill's colour system and type hierarchy set direction and thepptxskill's font, margin, and notes mechanics win. - External
datavizskill where installed: any chart or metric tile on a slide. ghostwriter: marketing copy outside a deck, and long-form prose from theblogprofile when the output is prose, not slides.ui-design: visual systems for product UI and landing pages; presentation visual rules live inreferences/visual-design.mdinstead.
Files in this skill
10presentation-creator skill questions
How do I install the presentation-creator skill in Claude Code?
Run npx degit mblode/agent-skills/skills/presentation-creator ~/.claude/skills/presentation-creator. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the presentation-creator skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
Can this skill create editable PowerPoint files?
No, this skill does not produce or edit .pptx files directly. It provides the outline, copy, and notes which should then be handed to an available presentation or PPTX skill.
What is the default output format for decks?
The skill defaults to Marp markdown unless specified otherwise.
How does the skill handle investor pitch decks differently?
For investor pitch decks sent to be read, it uses a specific 10-slide framework and async copy rules that replace the standard outline and writing steps.
How do I ensure my slides are readable during a live presentation?
The skill uses a 3-second test to ensure slides are parseable at arm's length and checks contrast ratios to ensure text is legible against backgrounds.