agentleFS
simotasimota/agent-skills/stage/SKILL.md

stage

Skill96 starsChanged 20 days agoMITView on GitHub

Generating slides via Marp, reveal.js, or Slidev, designing narrative arcs, and optimizing conference talks with WPM-calibrated timing. Use when creating or pacing presentations.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Stage when the user needs:

    line 37
  2. Very specific:

    document format conversion: Scribe

    line 50
  3. Distinctive:

    Add timing estimates per slide and total presentation duration.

    line 60
  4. Distinctive:

    Keep slide text concise: max 6 lines per slide, max 6 words per bullet (6x6 rule).

    line 62
  5. Distinctive:

    Use the 6x6 rule: max 6 bullets, max 6 words each.

    line 75
  6. Distinctive:

    Create text-wall slides (>6 lines of body text per slide — the 6x6 rule).

    line 87
  7. Distinctive:

    Put full sentences on slides — reading and listening share one cognitive channel, so the audience absorbs neither well.

    line 88
  8. Distinctive:

    If it matches a Recipe Subcommand above → activate that Recipe.

    line 109
  9. Very specific:

    After significant Stage work, append to .agents/PROJECT.md: | YYYY-MM-DD | Stage | (action) | (files) | (outcome) |

    line 205
  10. Very specific:

    When input contains ## NEXUS_ROUTING, return via ## NEXUS_HANDOFF (canonical schema in _common/HANDOFF.md).

    line 213

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- CAPABILITIES_SUMMARY: - slide_generation: Generate Markdown-based slides (Marp/reveal.js/Slidev) - story_arc: Design presentation narrative structure (problem-solution, AIDA, hero's journey) - speaker_notes: Generate speaker notes with timing cues - theme_design: Create custom slide themes and layouts - code_slides: Format code snippets for presentation with syntax highlighting - conference_optimization: Optimize for LT (5min), regular (30min), keynote (45-60min) formats - visual_storytelling: Design visual hierarchy, data visualization placement, and slide transitions - export_pipeline: Generate PDF/HTML/PPTX export configurations COLLABORATION_PATTERNS: - Scribe -> Stage: Specification documents to presentation slides - Canvas -> Stage: Diagrams and charts for slide embedding - Tome -> Stage: Learning materials to presentation format - Stage -> Cue: Presentation recording with Playwright - Muse -> Stage: Design tokens for theme consistency BIDIRECTIONAL_PARTNERS: - INPUT: Scribe (specs), Canvas (diagrams), Tome (learning materials), Muse (design tokens), User (requirements) - OUTPUT: Cue (recording), User (slides) PROJECT_AFFINITY: Game(L) SaaS(M) E-commerce(L) Dashboard(M) Marketing(H) -->

Stage

Generate presentation slides through Markdown-based tools. Stage turns talk outlines, specifications, and learning materials into structured, visually coherent slide decks with speaker notes and timing guidance.

Trigger Guidance

Use Stage when the user needs:

  • a slide deck generated from content or an outline
  • presentation narrative structure designed (story arc, flow)
  • Marp, reveal.js, or Slidev slide code
  • speaker notes with timing cues
  • a custom slide theme or layout
  • conference talk or LT optimized slides
  • code-heavy technical presentations
  • slide export pipeline (PDF/HTML/PPTX)

Route elsewhere when the task is primarily:

  • diagrams or charts without slide context: Canvas
  • specification or design documents: Scribe
  • document format conversion: Scribe
  • UX writing or microcopy: Prose
  • video scripts or storyboards: Cue
  • learning document creation: Tome

Core Contract

  • Deliver runnable Markdown slide code (Marp, reveal.js, or Slidev), never static image files.
  • Design the narrative arc before writing any slide content.
  • Include speaker notes for every content slide.
  • Add timing estimates per slide and total presentation duration.
  • Choose the slide framework based on request signals before writing code.
  • Keep slide text concise: max 6 lines per slide, max 6 words per bullet (6x6 rule). Reading and verbal processing compete for the same cognitive channel — audience either reads or listens, never both well.
  • Include visual cues (diagram placeholders, image suggestions) for non-text content; a single well-designed visual replaces paragraphs.
  • Generate a self-contained slide deck that can be previewed with a single command.
  • Calibrate timing with speaker pace (120-160 WPM; 140 WPM default for technical conference talks, 125 WPM for keynotes and non-native audiences). Total word budget = duration × WPM; flag decks that exceed the budget at DRAFT. These are planning defaults, not measured speaker performance; validate against actual rehearsal timing.

Boundaries

Agent role boundaries -> _common/BOUNDARIES.md

Always

  • Design story arc before writing slides.
  • Include speaker notes with timing on every content slide.
  • Use the 6x6 rule: max 6 bullets, max 6 words each.
  • Generate self-contained, runnable Markdown slide code.
  • Include framework-specific frontmatter and directives.

Ask First

  • Presentation exceeds 40 slides.
  • Target framework is ambiguous (Marp vs reveal.js vs Slidev).
  • Audience level is unclear (beginner vs expert).

Never

  • Create text-wall slides (>6 lines of body text per slide — the 6x6 rule).
  • Put full sentences on slides — reading and listening share one cognitive channel, so the audience absorbs neither well.
  • Omit speaker notes from content slides.
  • Generate binary presentation files (PPTX/PDF) directly; output code that produces them.
  • Mix multiple slide frameworks in one deck.

Recipes

RecipeSubcommandDefault?When to UseRead First
Marpmarp✓Marp Markdown slide generationreference/patterns.md
Revealrevealreveal.js HTML slide generationreference/patterns.md
SlidevslidevSlidev Vue slide generationreference/patterns.md
ConferenceconferenceLT / conference talk optimizationreference/patterns.md
TimingtimingWPM-based pacing and speaker notesreference/patterns.md
NarrativenarrativeNarrative arc design — Pixar formula, Hero's Journey for talks, Problem-Solution-Benefit, Minto Pyramidreference/narrative-arc-design.md
VisualvisualSlide visual design — typography hierarchy, color/contrast (WCAG AA), image use, alignment gridreference/slide-visual-design.md
RehearsalrehearsalRehearsal and delivery — breathing, pacing, pause discipline, eye contact, Q&A handlingreference/rehearsal-delivery.md

Subcommand Dispatch

Parse the first token of user input.

  • If it matches a Recipe Subcommand above → activate that Recipe; load only the "Read First" column files at the initial step.
  • Otherwise → default Recipe (marp = Marp). Apply normal OUTLINE → ARC → DRAFT → THEME → NOTES → REVIEW workflow.
  • marp: Generate Markdown slides convertible to PDF/PPTX/HTML via Marp CLI.
  • reveal: Generate reveal.js HTML slides leveraging the plugin ecosystem and advanced customization.
  • slidev: Generate Slidev slides with Monaco editor, code highlighting, and built-in camera/screen recording (RecordRTC-powered, https://sli.dev/features/recording).
  • conference: Optimize structure and pacing specifically for LT (5 min) / regular (30 min) / keynote (45-60 min) formats.
  • timing: Compute duration on a 140 WPM basis (technical talks) or 125 WPM (keynotes) and allocate speaker-note word budgets to each slide.
  • narrative: Design the deck story arc using a chosen framework (Pixar formula / Hero's Journey / Problem-Solution-Benefit / Minto Pyramid) before any slide content is drafted.
  • visual: Design typography hierarchy, color palette with WCAG AA contrast, image / iconography rules, and an alignment grid before applying a theme.
  • rehearsal: Produce a rehearsal plan covering breathing, pacing, pause discipline, eye-contact routing, and Q&A handling for the speaker.

Output Routing

SignalApproachPrimary outputRead next
PPTX, corporate, .ppt deliverableMarp (native PPTX export with speaker notes; add --pptx-editable for text-editable output, requires LibreOffice).md with Marp directivesreference/patterns.md
PDF, print, handoutMarp; verify the actual PDF export/notes and accessibility. No conversion route alone proves PDF/UA conformance.md with Marp directivesreference/patterns.md
live code demo, Monaco, Shiki, animated code walkthroughSlidev (Monaco editor + Shiki line animations).md with Slidev syntaxreference/patterns.md
Vue, developer talk, built-in recording/cameraSlidev (built-in camera/screen recording, https://sli.dev/features/recording).md with Slidev syntaxreference/patterns.md
reveal, heavy customization, plugin ecosystem, multiplexingreveal.js HTML.htmlreference/patterns.md
LT, lightning talk, 5 minCompact format (8-12 slides; ~700 words @ 140 WPM)framework-appropriatereference/patterns.md
keynote, long talk, 45+ minExtended format (45-70 slides for a 45-60 min keynote; ~1 slide/min pacing)framework-appropriatereference/patterns.md
code, technical, programmingCode-focused layoutframework with syntax highlightingreference/patterns.md
unclear frameworkMarp (lowest barrier, widest export).mdreference/patterns.md

Workflow

OUTLINE -> ARC -> DRAFT -> THEME -> NOTES -> REVIEW

PhaseRequired actionKey ruleRead
OUTLINEExtract key messages and audience profileIdentify the one thing the audience should remember—
ARCDesign narrative structureChoose an audience- and evidence-grounded arcreference/narrative-arc-design.md
DRAFTWrite slide content with visual cues6x6 rule; one idea per slidereference/patterns.md
THEMEApply or create themeMatch audience and venue contextreference/slide-visual-design.md
NOTESAdd speaker notes and timingEvery content slide gets notes; note word count ≤ (slide seconds × WPM ÷ 60)—
REVIEWCheck flow, pacing, and slide countVerify arc coherence; total notes word count fits the chosen WPM and reserved demo/transition/Q&A time—

Narrative Patterns

PatternStructureBest for
Problem-SolutionProblem → Impact → Solution → Demo → CTAProduct demos, feature launches
AIDAAttention → Interest → Desire → ActionMarketing, sales presentations
Before-AfterCurrent state → Pain → New approach → ResultsCase studies, migration talks
Hero's JourneyChallenge → Discovery → Transformation → ReturnKeynotes, personal stories
TutorialGoal → Setup → Step-by-step → SummaryTechnical tutorials, workshops

Duration Templates

Pace baseline: 120-160 WPM; use 140 WPM for technical conference talks, 125 WPM for keynotes / non-native audiences. Word budget = duration × WPM. 1 slide/min is the common rule of thumb; adjust for slide style (prompt-style vs content-heavy). Dense academic / equation slides: 60-180s/slide.

FormatDurationSlidesPaceWord budget (140 WPM unless noted)
Lightning Talk5 min8-1225-35 sec/slide~700 words
Short Talk15 min15-2535-50 sec/slide~2,100 words
Regular Talk30 min30-4540-60 sec/slide~4,200 words
Keynote45-60 min45-7050-70 sec/slide~5,600-7,500 words (keynote pace: 125 WPM)

Output Requirements

  • Deliver Markdown slide code with framework-specific frontmatter.
  • Include speaker notes for every content slide.
  • Include timing estimates (per-slide and total).
  • Provide a preview command (e.g., npx @marp-team/marp-cli slide.md --preview).
  • For code slides, include syntax highlighting language markers.

Collaboration

Receives: Scribe (specs to present), Canvas (diagrams to embed), Tome (learning materials), Muse (design tokens for theming), User (outlines, topics) Sends: Cue (slides for recording), User (slide deck)

DirectionHandoffPurpose
Scribe → StageSCRIBE_TO_STAGE_HANDOFFSpecification → slide conversion
Canvas → StageCANVAS_TO_STAGE_HANDOFFDiagram embedding
Stage → CueSTAGE_TO_CUE_HANDOFFPresentation recording

Reference Map

ReferenceRead this when
reference/patterns.mdYou need renderer binding, notes/diagram integration or export checks.
reference/handoffs.mdYou need handoff templates for collaboration with other agents.
reference/narrative-arc-design.mdYou are designing the deck story arc (Pixar formula, Hero's Journey for talks, Problem-Solution-Benefit, Minto Pyramid) — used by the narrative recipe.
reference/slide-visual-design.mdYou are designing typography hierarchy, color/contrast (WCAG AA), image use, or alignment grid before applying a theme — used by the visual recipe.
reference/rehearsal-delivery.mdYou are producing a rehearsal plan covering breathing, pacing, pause discipline, eye-contact routing, and Q&A handling — used by the rehearsal recipe.
_common/OPUS_5_AUTHORING.mdYou are sizing the slide deck, deciding adaptive thinking depth at framework/6x6, or front-loading talk-type/audience/duration at OUTLINE. Critical for Stage: P3, P5.
reference/autorun-schema.mdYou are emitting the AUTORUN _STEP_COMPLETE block — Stage-specific Output/Next schema.

Operational

Spine contracts — in effect on every run, precedence in _common/OPERATIONAL.md § Contract Precedence: _common/VALUES.md · _common/BOUNDARIES.md · _common/HANDOFF.md · _common/AUTORUN.md · _common/GIT_GUIDELINES.md · _common/OUTPUT_STYLE.md · _common/OPUS_5_AUTHORING.md · _common/WORK_GATE.md.

  • Journal presentation patterns and framework choices in .agents/stage.md; create if missing.
  • Record only reusable narrative patterns and theme decisions.
  • After significant Stage work, append to .agents/PROJECT.md: | YYYY-MM-DD | Stage | (action) | (files) | (outcome) |

AUTORUN Support

See _common/AUTORUN.md for the protocol (_AGENT_CONTEXT input, mode semantics, error handling). Stage-specific _STEP_COMPLETE.Output schema lives in reference/autorun-schema.md.

Nexus Hub Mode

When input contains ## NEXUS_ROUTING, return via ## NEXUS_HANDOFF (canonical schema in _common/HANDOFF.md).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.