跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
演示文稿

presentation-creator

Builds decks with a story spine, house visual system, setting-specific density, and speaker notes. Use when asked to "create a presentation", "write a pitch deck", or "turn this doc into slides". Defaults to Marp; use an available presentation tool for editable PowerPoint. For product UI use ui-design.

mblode · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add mblode/agent-skills --skill presentation-creator

技能说明


name: presentation-creator description: Builds decks with a story spine, house visual system, setting-specific density, and speaker notes. Use when asked to "create a presentation", "write a pitch deck", or "turn this doc into slides". Defaults to Marp; use an available presentation tool for editable PowerPoint. For product UI use ui-design.

Presentation 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/.potx file itself (available presentation/PPTX skill or tool; hand it the finished outline, copy, and notes from this skill), charts inside a slide (external dataviz where installed), long-form prose (external ghostwriter with platform blog), marketing copy outside slides (copywriting), 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 .pptx when the user names the file or a house template, produced by the external pptx skill 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.md at 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:

StepReferenceCovers
2. Storyreferences/story-structure.mdThe spine template, writing the ending first, taking a position, stakes, the unstick move
3. Outlinereferences/outline-structure.mdNarrative flow, 12 slide types, section colours, outline output format
4. Writereferences/writing-slides.md, replaced by references/pitch-decks.md on the pitch pathHeadline patterns, body rules, copy per slide type, before/after examples
5. Designreferences/visual-design.mdTwo colour systems, contrast thresholds, fluid and fixed type scales, layout patterns, slide type to layout mapping
6. Notesreferences/speaker-notes.mdPer-slide note structure, delivery cues, notes by slide type
7. Emitreferences/output-formats.mdMarp syntax and export, Slidev and reveal.js equivalents, the pptx handoff, where notes live in each
7. Emit (web)references/web-deck.mdRoute-per-slide structure, navigation, layout primitives, motion, live demos
Changing this skillevals/evals.jsonBehavioural scenarios with assertions, plus should-trigger and near-miss routing prompts. 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 yo
阅读完整来源 ↗