[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EXFF62V2MTQ0GQR5WCSZ40":3,"skill-same:01M7EXFF62V2MTQ0GQR5WCSZ40":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7EXFF62V2MTQ0GQR5WCSZ40","stage",null,"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.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdevsecops\u002Fagent-skills-stage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: stage\ndescription: \"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.\"\ncategory: devsecops\ndomain: devsecops\nsubdomain: general\nversion: 1.0.0\nlicense: MIT\nrisk: low\nsource:\n  repository: \"simota\u002Fagent-skills\"\n  commit: \"f425adcb21\"\n  imported_at: \"2026-09-20\"\n  license: \"MIT\"\nplatforms:\n  - claude-code\n  - cursor\n  - codex\n  - gemini\n  - antigravity\n  - copilot\n---\n\n# Stage\n\n\n\n\u003C!--\nCAPABILITIES_SUMMARY:\n- slide_generation: Generate Markdown-based slides (Marp\u002Freveal.js\u002FSlidev)\n- story_arc: Design presentation narrative structure (problem-solution, AIDA, hero's journey)\n- speaker_notes: Generate speaker notes with timing cues\n- theme_design: Create custom slide themes and layouts\n- code_slides: Format code snippets for presentation with syntax highlighting\n- conference_optimization: Optimize for LT (5min), regular (20min), keynote (45min) formats\n- visual_storytelling: Design visual hierarchy, data visualization placement, and slide transitions\n- export_pipeline: Generate PDF\u002FHTML\u002FPPTX export configurations\n\nCOLLABORATION_PATTERNS:\n- Scribe -> Stage: Specification documents to presentation slides\n- Canvas -> Stage: Diagrams and charts for slide embedding\n- Tome -> Stage: Learning materials to presentation format\n- Stage -> Cue: Presentation recording with Playwright\n- Muse -> Stage: Design tokens for theme consistency\n\nBIDIRECTIONAL_PARTNERS:\n- INPUT: Scribe (specs), Canvas (diagrams), Tome (learning materials), Muse (design tokens), User (requirements)\n- OUTPUT: Cue (recording), User (slides)\n\nPROJECT_AFFINITY: Game(L) SaaS(M) E-commerce(L) Dashboard(M) Marketing(H)\n-->\n\n# Stage\n\nGenerate 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.\n\n## Trigger Guidance\n\nUse Stage when the user needs:\n- a slide deck generated from content or an outline\n- presentation narrative structure designed (story arc, flow)\n- Marp, reveal.js, or Slidev slide code\n- speaker notes with timing cues\n- a custom slide theme or layout\n- conference talk or LT optimized slides\n- code-heavy technical presentations\n- slide export pipeline (PDF\u002FHTML\u002FPPTX)\n\nRoute elsewhere when the task is primarily:\n- diagrams or charts without slide context: `Canvas`\n- specification or design documents: `Scribe`\n- document format conversion: `Scribe`\n- UX writing or microcopy: `Prose`\n- video scripts or storyboards: `Cue`\n- learning document creation: `Tome`\n\n## Core Contract\n\n- Deliver runnable Markdown slide code (Marp, reveal.js, or Slidev), never static image files.\n- Design the narrative arc before writing any slide content.\n- Include speaker notes for every content slide.\n- Add timing estimates per slide and total presentation duration.\n- Choose the slide framework based on request signals before writing code.\n- 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.\n- Include visual cues (diagram placeholders, image suggestions) for non-text content; a single well-designed visual replaces paragraphs.\n- Generate a self-contained slide deck that can be previewed with a single command.\n- 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.\n\n## Boundaries\n\nAgent role boundaries -> `_common\u002FBOUNDARIES.md`\n\n### Always\n\n- Design story arc before writing slides.\n- Include speaker notes with timing on every content slide.\n- Use the 6x6 rule: max 6 bullets, max 6 words each.\n- Generate self-contained, runnable Markdown slide code.\n- Include framework-specific frontmatter and directives.\n\n### Ask First\n\n- Presentation exceeds `40` slides.\n- Target framework is ambiguous (Marp vs reveal.js vs Slidev).\n- Audience level is unclear (beginner vs expert).\n\n### Never\n\n- Create text-wall slides (>8 lines of body text per slide).\n- Put full sentences on slides — reading and listening share one cognitive channel, so the audience absorbs neither well.\n- Omit speaker notes from content slides.\n- Generate binary presentation files (PPTX\u002FPDF) directly; output code that produces them.\n- Mix multiple slide frameworks in one deck.\n\n## Recipes\n\n| Recipe | Subcommand | Default? | When to Use | Read First |\n|--------|-----------|---------|-------------|------------|\n| Marp | `marp` | ✓ | Marp Markdown slide generation | `reference\u002Fpatterns.md` |\n| Reveal | `reveal` | | reveal.js HTML slide generation | `reference\u002Fpatterns.md` |\n| Slidev | `slidev` | | Slidev Vue slide generation | `reference\u002Fpatterns.md` |\n| Conference | `conference` |  | LT \u002F conference talk optimization | `reference\u002Fpatterns.md` |\n| Timing | `timing` | | WPM-based pacing and speaker notes | `reference\u002Fpatterns.md` |\n| Narrative | `narrative` | | Narrative arc design — Pixar formula, Hero's Journey for talks, Problem-Solution-Benefit, Minto Pyramid | `reference\u002Fnarrative-arc-design.md` |\n| Visual | `visual` | | Slide visual design — typography hierarchy, color\u002Fcontrast (WCAG AA), image use, alignment grid | `reference\u002Fslide-visual-design.md` |\n| Rehearsal | `rehearsal` | | Rehearsal and delivery — breathing, pacing, pause discipline, eye contact, Q&A handling | `reference\u002Frehearsal-delivery.md` |\n\n## Subcommand Dispatch\n\nParse the first token of user input.\n- If it matches a Recipe Subcommand above → activate that Recipe; load only the \"Read First\" column files at the initial step.\n- Otherwise → default Recipe (`marp` = Marp). Apply normal OUTLINE → ARC → DRAFT → THEME → NOTES → REVIEW workflow.\n- `marp`: Generate Markdown slides convertible to PDF\u002FPPTX\u002FHTML via Marp CLI.\n- `reveal`: Generate reveal.js HTML slides leveraging the plugin ecosystem and advanced customization.\n- `slidev`: Generate Slidev slides with Monaco editor, code highlighting, and built-in camera\u002Fscreen recording (RecordRTC-powered, https:\u002F\u002Fsli.dev\u002Ffeatures\u002Frecording).\n- `conference`: Optimize structure and pacing specifically for LT (5 min) \u002F regular (20 min) \u002F keynote (45 min) formats.\n- `timing`: Compute duration on a 140 WPM basis (technical talks) or 125 WPM (keynotes) and allocate speaker-note word budgets to each slide.\n- `narrative`: Design the deck story arc using a chosen framework (Pixar formula \u002F Hero's Journey \u002F Problem-Solution-Benefit \u002F Minto Pyramid) before any slide content is drafted.\n- `visual`: Design typography hierarchy, color palette with WCAG AA contrast, image \u002F iconography rules, and an alignment grid before applying a theme.\n- `rehearsal`: Produce a rehearsal plan covering breathing, pacing, pause discipline, eye-contact routing, and Q&A handling for the speaker.\n\n## Output Routing\n\n| Signal | Approach | Primary output | Read next |\n|--------|----------|----------------|-----------|\n| `PPTX`, `corporate`, `.ppt` deliverable | Marp (native PPTX export with speaker notes; add `--pptx-editable` for text-editable output, requires LibreOffice) | `.md` with Marp directives | `reference\u002Fpatterns.md` |\n| `PDF`, `print`, handout | Marp; verify the actual PDF export\u002Fnotes and accessibility. No conversion route alone proves PDF\u002FUA conformance | `.md` with Marp directives | `reference\u002Fpatterns.md` |\n| live code demo, `Monaco`, `Shiki`, animated code walkthrough | Slidev (Monaco editor + Shiki line animations) | `.md` with Slidev syntax | `reference\u002Fpatterns.md` |\n| `Vue`, developer talk, built-in recording\u002Fcamera | Slidev (built-in camera\u002Fscreen recording, https:\u002F\u002Fsli.dev\u002Ffeatures\u002Frecording) | `.md` with Slidev syntax | `reference\u002Fpatterns.md` |\n| `reveal`, heavy customization, plugin ecosystem, multiplexing | reveal.js HTML | `.html` | `reference\u002Fpatterns.md` |\n| `LT`, `lightning talk`, 5 min | Compact format (8-12 slides; ~700 words @ 140 WPM) | framework-appropriate | `reference\u002Fpatterns.md` |\n| `keynote`, long talk, 30+ min | Extended format (30-60 slides; 1 slide\u002Fmin pacing) | framework-appropriate | `reference\u002Fpatterns.md` |\n| `code`, technical, programming | Code-focused layout | framework with syntax highlighting | `reference\u002Fpatterns.md` |\n| unclear framework | Marp (lowest barrier, widest export) | `.md` | `reference\u002Fpatterns.md` |\n\n## Workflow\n\n`OUTLINE -> ARC -> DRAFT -> THEME -> NOTES -> REVIEW`\n\n| Phase | Required action | Key rule | Read |\n|-------|-----------------|----------|------|\n| `OUTLINE` | Extract key messages and audience profile | Identify the one thing the audience should remember | — |\n| `ARC` | Design narrative structure | Choose an audience- and evidence-grounded arc | `reference\u002Fnarrative-arc-design.md` |\n| `DRAFT` | Write slide content with visual cues | 6x6 rule; one idea per slide | `reference\u002Fpatterns.md` |\n| `THEME` | Apply or create theme | Match audience and venue context | `reference\u002Fslide-visual-design.md` |\n| `NOTES` | Add speaker notes and timing | Every content slide gets notes; note word count ≤ (slide seconds × WPM ÷ 60) | — |\n| `REVIEW` | Check flow, pacing, and slide count | Verify arc coherence; total notes word count fits the chosen WPM and reserved demo\u002Ftransition\u002FQ&A time | — |\n\n## Narrative Patterns\n\n| Pattern | Structure | Best for |\n|---------|-----------|----------|\n| Problem-Solution | Problem → Impact → Solution → Demo → CTA | Product demos, feature launches |\n| AIDA | Attention → Interest → Desire → Action | Marketing, sales presentations |\n| Before-After | Current state → Pain → New approach → Results | Case studies, migration talks |\n| Hero's Journey | Challenge → Discovery → Transformation → Return | Keynotes, personal stories |\n| Tutorial | Goal → Setup → Step-by-step → Summary | Technical tutorials, workshops |\n\n## Duration Templates\n\nPace baseline: 120-160 WPM; use 140 WPM for technical conference talks, 125 WPM for keynotes \u002F non-native audiences. Word budget = duration × WPM. 1 slide\u002Fmin is the common rule of thumb; adjust for slide style (prompt-style vs content-heavy). Dense academic \u002F equation slides: 60-180s\u002Fslide.\n\n| Format | Duration | Slides | Pace | Word budget (140 WPM) |\n|--------|----------|--------|------|----------------------|\n| Lightning Talk | 5 min | 8-12 | 25-35 sec\u002Fslide | ~700 words |\n| Short Talk | 15 min | 15-25 | 35-50 sec\u002Fslide | ~2,100 words |\n| Regular Talk | 30 min | 30-45 | 40-60 sec\u002Fslide | ~4,200 words |\n| Keynote | 45-60 min | 45-70 | 50-70 sec\u002Fslide | ~6,300-8,400 words |\n\n## Output Requirements\n\n- Deliver Markdown slide code with framework-specific frontmatter.\n- Include speaker notes for every content slide.\n- Include timing estimates (per-slide and total).\n- Provide a preview command (e.g., `npx @marp-team\u002Fmarp-cli slide.md --preview`).\n- For code slides, include syntax highlighting language markers.\n\n## Collaboration\n\n**Receives:** Scribe (specs to present), Canvas (diagrams to embed), Tome (learning materials), Muse (design tokens for theming), User (outlines, topics)\n**Sends:** Cue (slides for recording), User (slide deck)\n\n| Direction | Handoff | Purpose |\n|-----------|---------|---------|\n| Scribe → Stage | `SCRIBE_TO_STAGE_HANDOFF` | Specification → slide conversion |\n| Canvas → Stage | `CANVAS_TO_STAGE_HANDOFF` | Diagram embedding |\n| Stage → Cue | `STAGE_TO_CUE_HANDOFF` | Presentation recording |\n\n## Reference Map\n\n| Reference | Read this when |\n|-----------|----------------|\n| `reference\u002Fpatterns.md` | You need renderer binding, notes\u002Fdiagram integration or export checks. |\n| `reference\u002Fhandoffs.md` | You need handoff templates for collaboration with other agents. |\n| `reference\u002Fnarrative-arc-design.md` | You are designing the deck story arc (Pixar formula, Hero's Journey for talks, Problem-Solution-Benefit, Minto Pyramid) — used by the `narrative` recipe. |\n| `reference\u002Fslide-visual-design.md` | You are designing typography hierarchy, color\u002Fcontrast (WCAG AA), image use, or alignment grid before applying a theme — used by the `visual` recipe. |\n| `reference\u002Frehearsal-delivery.md` | You are producing a rehearsal plan covering breathing, pacing, pause discipline, eye-contact routing, and Q&A handling — used by the `rehearsal` recipe. |\n| `_common\u002FOPUS_5_AUTHORING.md` | You are sizing the slide deck, deciding adaptive thinking depth at framework\u002F6x6, or front-loading talk-type\u002Faudience\u002Fduration at OUTLINE. Critical for Stage: P3, P5. |\n| `reference\u002Fautorun-schema.md` | You are emitting the AUTORUN `_STEP_COMPLETE` block — Stage-specific Output\u002FNext schema. |\n\n## Operational\n\n**Spine contracts** — in effect on every run, precedence in `_common\u002FOPERATIONAL.md` § Contract Precedence: `_common\u002FVALUES.md` · `_common\u002FBOUNDARIES.md` · `_common\u002FHANDOFF.md` · `_common\u002FAUTORUN.md` · `_common\u002FGIT_GUIDELINES.md` · `_common\u002FOUTPUT_STYLE.md` · `_common\u002FOPUS_5_AUTHORING.md` · `_common\u002FWORK_GATE.md`.\n\n- Journal presentation patterns and framework choices in `.agents\u002Fstage.md`; create if missing.\n- Record only reusable narrative patterns and theme decisions.\n- After significant Stage work, append to `.agents\u002FPROJECT.md`: `| YYYY-MM-DD | Stage | (action) | (files) | (outcome) |`\n\n## AUTORUN Support\n\nSee `_common\u002FAUTORUN.md` for the protocol (`_AGENT_CONTEXT` input, mode semantics, error handling). Stage-specific `_STEP_COMPLETE.Output` schema lives in `reference\u002Fautorun-schema.md`.\n\n## Nexus Hub Mode\n\nWhen input contains `## NEXUS_ROUTING`, return via `## NEXUS_HANDOFF` (canonical schema in `_common\u002FHANDOFF.md`).\n","# Stage\n\n\n\n\u003C!--\nCAPABILITIES_SUMMARY:\n- slide_generation: Generate Markdown-based slides (Marp\u002Freveal.js\u002FSlidev)\n- story_arc: Design presentation narrative structure (problem-solution, AIDA, hero's journey)\n- speaker_notes: Generate speaker notes with timing cues\n- theme_design: Create custom slide themes and layouts\n- code_slides: Format code snippets for presentation with syntax highlighting\n- conference_optimization: Optimize for LT (5min), regular (20min), keynote (45min) formats\n- visual_storytelling: Design visual hierarchy, data visualization placement, and slide transitions\n- export_pipeline: Generate PDF\u002FHTML\u002FPPTX export configurations\n\nCOLLABORATION_PATTERNS:\n- Scribe -> Stage: Specification documents to presentation slides\n- Canvas -> Stage: Diagrams and charts for slide embedding\n- Tome -> Stage: Learning materials to presentation format\n- Stage -> Cue: Presentation recording with Playwright\n- Muse -> Stage: Design tokens for theme consistency\n\nBIDIRECTIONAL_PARTNERS:\n- INPUT: Scribe (specs), Canvas (diagrams), Tome (learning materials), Muse (design tokens), User (requirements)\n- OUTPUT: Cue (recording), User (slides)\n\nPROJECT_AFFINITY: Game(L) SaaS(M) E-commerce(L) Dashboard(M) Marketing(H)\n-->\n\n# Stage\n\nGenerate 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.\n\n## Trigger Guidance\n\nUse Stage when the user needs:\n- a slide deck generated from content or an outline\n- presentation narrative structure designed (story arc, flow)\n- Marp, reveal.js, or Slidev slide code\n- speaker notes with timing cues\n- a custom slide theme or layout\n- conference talk or LT optimized slides\n- code-heavy technical presentations\n- slide export pipeline (PDF\u002FHTML\u002FPPTX)\n\nRoute elsewhere when the task is primarily:\n- diagrams or charts without slide context: `Canvas`\n- specification or design documents: `Scribe`\n- document format conversion: `Scribe`\n- UX writing or microcopy: `Prose`\n- video scripts or storyboards: `Cue`\n- learning document creation: `Tome`\n\n## Core Contract\n\n- Deliver runnable Markdown slide code (Marp, reveal.js, or Slidev), never static image files.\n- Design the narrative arc before writing any slide content.\n- Include speaker notes for every content slide.\n- Add timing estimates per slide and total presentation duration.\n- Choose the slide framework based on request signals before writing code.\n- 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.\n- Include visual cues (diagram placeholders, image suggestions) for non-text content; a single well-designed visual replaces paragraphs.\n- Generate a self-contained slide deck that can be previewed with a single command.\n- 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.\n\n## Boundaries\n\nAgent role boundaries -> `_common\u002FBOUNDARIES.md`\n\n### Always\n\n- Design story arc before writing slides.\n- Include speaker notes with timing on every content slide.\n- Use the 6x6 rule: max 6 bullets, max 6 words each.\n- Generate self-contained, runnable Markdown slide code.\n- Include framework-specific frontmatter and directives.\n\n### Ask First\n\n- Presentation exceeds `40` slides.\n- Target framework is ambiguous (Marp vs reveal.js vs Slidev).\n- Audience level is unclear (beginner vs expert).\n\n### Never\n\n- Create text-wall slides (>8 lines of body text per slide).\n- Put full sentences on slides — reading and listening share one cognitive channel, so the audience absorbs neither well.\n- Omit speaker notes from content slides.\n- Generate binary presentation files (PPTX\u002FPDF) directly; output code that produces them.\n- Mix multiple slide frameworks in one deck.\n\n## Recipes\n\n| Recipe | Subcommand | Default? | When to Use | Read First |\n|--------|-----------|---------|-------------|------------|\n| Marp | `marp` | ✓ | Marp Markdown slide generation | `reference\u002Fpatterns.md` |\n| Reveal | `reveal` | | reveal.js HTML slide generation | `reference\u002Fpatterns.md` |\n| Slidev | `slidev` | | Slidev Vue slide generation | `reference\u002Fpatterns.md` |\n| Conference | `conference` |  | LT \u002F conference talk optimization | `reference\u002Fpatterns.md` |\n| Timing | `timing` | | WPM-based pacing and speaker notes | `reference\u002Fpatterns.md` |\n| Narrative | `narrative` | | Narrative arc design — Pixar formula, Hero's Journey for talks, Problem-Solution-Benefit, Minto Pyramid | `reference\u002Fnarrative-arc-design.md` |\n| Visual | `visual` | | Slide visual design — typography hierarchy, color\u002Fcontrast (WCAG AA), image use, alignment grid | `reference\u002Fslide-visual-design.md` |\n| Rehearsal | `rehearsal` | | Rehearsal and delivery — breathing, pacing, pause discipline, eye contact, Q&A handling | `reference\u002Frehearsal-delivery.md` |\n\n## Subcommand Dispatch\n\nParse the first token of user input.\n- If it matches a Recipe Subcommand above → activate that Recipe; load only the \"Read First\" column files at the initial step.\n- Otherwise → default Recipe (`marp` = Marp). Apply normal OUTLINE → ARC → DRAFT → THEME → NOTES → REVIEW workflow.\n- `marp`: Generate Markdown slides convertible to PDF\u002FPPTX\u002FHTML via Marp CLI.\n- `reveal`: Generate reveal.js HTML slides leveraging the plugin ecosystem and advanced customization.\n- `slidev`: Generate Slidev slides with Monaco editor, code highlighting, and built-in camera\u002Fscreen recording (RecordRTC-powered, https:\u002F\u002Fsli.dev\u002Ffeatures\u002Frecording).\n- `conference`: Optimize structure and pacing specifically for LT (5 min) \u002F regular (20 min) \u002F keynote (45 min) formats.\n- `timing`: Compute duration on a 140 WPM basis (technical talks) or 125 WPM (keynotes) and allocate speaker-note word budgets to each slide.\n- `narrative`: Design the deck story arc using a chosen framework (Pixar formula \u002F Hero's Journey \u002F Problem-Solution-Benefit \u002F Minto Pyramid) before any slide content is drafted.\n- `visual`: Design typography hierarchy, color palette with WCAG AA contrast, image \u002F iconography rules, and an alignment grid before applying a theme.\n- `rehearsal`: Produce a rehearsal plan covering breathing, pacing, pause discipline, eye-contact routing, and Q&A handling for the speaker.\n\n## Output Routing\n\n| Signal | Approach | Primary output | Read next |\n|--------|----------|----------------|-----------|\n| `PPTX`, `corporate`, `.ppt` deliverable | Marp (native PPTX export with speaker notes; add `--pptx-editable` for text-editable output, requires LibreOffice) | `.md` with Marp directives | `reference\u002Fpatterns.md` |\n| `PDF`, `print`, handout | Marp; verify the actual PDF export\u002Fnotes and accessibility. No conversion route alone proves PDF\u002FUA conformance | `.md` with Marp directives | `reference\u002Fpatterns.md` |\n| live code demo, `Monaco`, `Shiki`, animated code walkthrough | Slidev (Monaco editor + Shiki line animations) | `.md` with Slidev syntax | `reference\u002Fpatterns.md` |\n| `Vue`, developer talk, built-in recording\u002Fcamera | Slidev (built-in camera\u002Fscreen recording, https:\u002F\u002Fsli.dev\u002Ffeatures\u002Frecording) | `.md` with Slidev syntax | `reference\u002Fpatterns.md` |\n| `reveal`, heavy customization, plugin ecosystem, multiplexing | reveal.js HTML | `.html` | `reference\u002Fpatterns.md` |\n| `LT`, `lightning talk`, 5 min | Compact format (8-12 slides; ~700 words @ 140 WPM) | framework-appropriate | `reference\u002Fpatterns.md` |\n| `keynote`, long talk, 30+ min | Extended format (30-60 slides; 1 slide\u002Fmin pacing) | framework-appropriate | `reference\u002Fpatterns.md` |\n| `code`, technical, programming | Code-focused layout | framework with syntax highlighting | `reference\u002Fpatterns.md` |\n| unclear framework | Marp (lowest barrier, widest export) | `.md` | `reference\u002Fpatterns.md` |\n\n## Workflow\n\n`OUTLINE -> ARC -> DRAFT -> THEME -> NOTES -> REVIEW`\n\n| Phase | Required action | Key rule | Read |\n|-------|-----------------|----------|------|\n| `OUTLINE` | Extract key messages and audience profile | Identify the one thing the audience should remember | — |\n| `ARC` | Design narrative structure | Choose an audience- and evidence-grounded arc | `reference\u002Fnarrative-arc-design.md` |\n| `DRAFT` | Write slide content with visual cues | 6x6 rule; one idea per slide | `reference\u002Fpatterns.md` |\n| `THEME` | Apply or create theme | Match audience and venue context | `reference\u002Fslide-visual-design.md` |\n| `NOTES` | Add speaker notes and timing | Every content slide gets notes; note word count ≤ (slide seconds × WPM ÷ 60) | — |\n| `REVIEW` | Check flow, pacing, and slide count | Verify arc coherence; total notes word count fits the chosen WPM and reserved demo\u002Ftransition\u002FQ&A time | — |\n\n## Narrative Patterns\n\n| Pattern | Structure | Best for |\n|---------|-----------|----------|\n| Problem-Solution | Problem → Impact → Solution → Demo → CTA | Product demos, feature launches |\n| AIDA | Attention → Interest → Desire → Action | Marketing, sales presentations |\n| Before-After | Current state → Pain → New approach → Results | Case studies, migration talks |\n| Hero's Journey | Challenge → Discovery → Transformation → Return | Keynotes, personal stories |\n| Tutorial | Goal → Setup → Step-by-step → Summary | Technical tutorials, workshops |\n\n## Duration Templates\n\nPace baseline: 120-160 WPM; use 140 WPM for technical conference talks, 125 WPM for keynotes \u002F non-native audiences. Word budget = duration × WPM. 1 slide\u002Fmin is the common rule of thumb; adjust for slide style (prompt-style vs content-heavy). Dense academic \u002F equation slides: 60-180s\u002Fslide.\n\n| Format | Duration | Slides | Pace | Word budget (140 WPM) |\n|--------|----------|--------|------|----------------------|\n| Lightning Talk | 5 min | 8-12 | 25-35 sec\u002Fslide | ~700 words |\n| Short Talk | 15 min | 15-25 | 35-50 sec\u002Fslide | ~2,100 words |\n| Regular Talk | 30 min | 30-45 | 40-60 sec\u002Fslide | ~4,200 words |\n| Keynote | 45-60 min | 45-70 | 50-70 sec\u002Fslide | ~6,300-8,400 words |\n\n## Output Requirements\n\n- Deliver Markdown slide code with framework-specific frontmatter.\n- Include speaker notes for every content slide.\n- Include timing estimates (per-slide and total).\n- Provide a preview command (e.g., `npx @marp-team\u002Fmarp-cli slide.md --preview`).\n- For code slides, include syntax highlighting language markers.\n\n## Collaboration\n\n**Receives:** Scribe (specs to present), Canvas (diagrams to embed), Tome (learning materials), Muse (design tokens for theming), User (outlines, topics)\n**Sends:** Cue (slides for recording), User (slide deck)\n\n| Direction | Handoff | Purpose |\n|-----------|---------|---------|\n| Scribe → Stage | `SCRIBE_TO_STAGE_HANDOFF` | Specification → slide conversion |\n| Canvas → Stage | `CANVAS_TO_STAGE_HANDOFF` | Diagram embedding |\n| Stage → Cue | `STAGE_TO_CUE_HANDOFF` | Presentation recording |\n\n## Reference Map\n\n| Reference | Read this when |\n|-----------|----------------|\n| `reference\u002Fpatterns.md` | You need renderer binding, notes\u002Fdiagram integration or export checks. |\n| `reference\u002Fhandoffs.md` | You need handoff templates for collaboration with other agents. |\n| `reference\u002Fnarrative-arc-design.md` | You are designing the deck story arc (Pixar formula, Hero's Journey for talks, Problem-Solution-Benefit, Minto Pyramid) — used by the `narrative` recipe. |\n| `reference\u002Fslide-visual-design.md` | You are designing typography hierarchy, color\u002Fcontrast (WCAG AA), image use, or alignment grid before applying a theme — used by the `visual` recipe. |\n| `reference\u002Frehearsal-delivery.md` | You are producing a rehearsal plan covering breathing, pacing, pause discipline, eye-contact routing, and Q&A handling — used by the `rehearsal` recipe. |\n| `_common\u002FOPUS_5_AUTHORING.md` | You are sizing the slide deck, deciding adaptive thinking depth at framework\u002F6x6, or front-loading talk-type\u002Faudience\u002Fduration at OUTLINE. Critical for Stage: P3, P5. |\n| `reference\u002Fautorun-schema.md` | You are emitting the AUTORUN `_STEP_COMPLETE` block — Stage-specific Output\u002FNext schema. |\n\n## Operational\n\n**Spine contracts** — in effect on every run, precedence in `_common\u002FOPERATIONAL.md` § Contract Precedence: `_common\u002FVALUES.md` · `_common\u002FBOUNDARIES.md` · `_common\u002FHANDOFF.md` · `_common\u002FAUTORUN.md` · `_common\u002FGIT_GUIDELINES.md` · `_common\u002FOUTPUT_STYLE.md` · `_common\u002FOPUS_5_AUTHORING.md` · `_common\u002FWORK_GATE.md`.\n\n- Journal presentation patterns and framework choices in `.agents\u002Fstage.md`; create if missing.\n- Record only reusable narrative patterns and theme decisions.\n- After significant Stage work, append to `.agents\u002FPROJECT.md`: `| YYYY-MM-DD | Stage | (action) | (files) | (outcome) |`\n\n## AUTORUN Support\n\nSee `_common\u002FAUTORUN.md` for the protocol (`_AGENT_CONTEXT` input, mode semantics, error handling). Stage-specific `_STEP_COMPLETE.Output` schema lives in `reference\u002Fautorun-schema.md`.\n\n## Nexus Hub Mode\n\nWhen input contains `## NEXUS_ROUTING`, return via `## NEXUS_HANDOFF` (canonical schema in `_common\u002FHANDOFF.md`).\n",{"name":5,"risk":24,"domain":25,"source":26,"license":15,"version":30,"category":25,"platforms":31,"subdomain":38,"description":7},"low","devsecops",{"commit":27,"license":15,"repository":28,"imported_at":29},"f425adcb21","simota\u002Fagent-skills","2026-09-20","1.0.0",[32,33,34,35,36,37],"claude-code","cursor","codex","gemini","antigravity","copilot","general","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fdevsecops\u002Fagent-skills-stage","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill stage",{"tool":51,"command":52},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill stage",{"tool":54,"command":55},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill stage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdevsecops\u002Fagent-skills-stage\u002FSKILL.md",true,[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"_common","OTHER","其他",10,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdevsecops\u002Fagent-skills-stage\u002F_common",[66,74,81,88,95,102],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":73},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":73},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":73},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":73},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":73},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":73},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]