slides
Generate Marp-compatible slide decks from a structured JSON schema. Use when the user asks for slides, a presentation, a demo deck, sprint review slides, or a tech talk. Converts project context into presentations for talks, demos, and tutorials.
Install
npx skills add https://github.com/Rune-kit/rune/tree/master/skills/slides
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install rune-kit-rune@llmmart
git clone https://github.com/Rune-kit/rune.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole rune-kit/rune collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
slides
Purpose
Generates structured slide decks as Marp-compatible markdown. The agent analyzes context (feature, sprint, tutorial) and produces a JSON slide schema, then calls build-deck.js to convert it to presentation-ready markdown. The script standardizes output format — preventing agent freestyle errors when context runs low.
Triggers
- User says "create slides", "make presentation", "demo deck", "sprint review slides", "tech talk"
/rune slides— manual invocation- Called by other skills needing presentation output
Called By (inbound)
marketing(L2): launch presentations, product demosvideo-creator(L3): slide-based video storyboards- User: direct invocation
Calls (outbound)
None — pure L3 utility.
Executable Instructions
Step 1: Analyze Context
Determine the presentation type from the user's request:
| Context | Template | Typical Slides |
|---|---|---|
| Feature demo | Demo walkthrough | Problem → Solution → Architecture → Live demo → Next steps |
| Sprint review | Sprint summary | Goals → Completed → Metrics → Blockers → Next sprint |
| Tech talk | Teaching format | Hook → Concept → Deep dive → Code examples → Takeaways |
| Tutorial | Step-by-step | Intro → Prerequisites → Step 1-N → Summary → Resources |
| Pitch | Persuasion | Problem → Market → Solution → Traction → Ask |
Step 2: Generate JSON Schema
Create a JSON file following this schema:
{
"title": "Presentation Title",
"author": "Author Name (optional)",
"theme": "default|gaia|uncover",
"slides": [
{
"type": "title|content|code|diagram|image|quote|section",
"heading": "Slide Heading",
"body": "Markdown body text",
"notes": "Speaker notes (optional)",
"code": { "lang": "javascript", "source": "console.log('hi')" },
"diagram": "graph LR; A-->B"
}
]
}
Slide types:
title— opening slide with# headingcontent— standard slide with## heading+ bodycode— slide with syntax-highlighted code blockdiagram— slide with Mermaid diagram (stays a Mermaid fence for Marp; do NOT replace with adiagram-generated HTML here)image— slide with image reference in bodyquote— slide with blockquote formattingsection— section divider with# heading
Save the JSON to a temporary file (e.g., slides.json).
Step 3: Build Deck
Execute the build script:
node {scripts_dir}/build-deck.js --input slides.json --output deck.md
The script outputs Marp-compatible markdown with:
- Marp frontmatter (
marp: true, theme) - Slide separators (
---) - Speaker notes as HTML comments
- Code blocks with language hints
- Mermaid diagram blocks
Step 4: Present Result
Show the user:
- The generated
deck.mdfile path - How to preview:
npx @marp-team/marp-cli deck.md --preview(or any Marp viewer) - How to export PDF:
npx @marp-team/marp-cli deck.md --pdf
Fallback: If {scripts_dir}/build-deck.js is unavailable, generate the Marp markdown directly — the script is an optimization, not a hard dependency.
Output Format
---
marp: true
theme: default
---
# Presentation Title
Author Name
---
## Slide Heading
Slide body content
<!-- notes: Speaker notes here -->
Sharp Edges
| Failure Mode | Severity | Mitigation |
|---|---|---|
| build-deck.js not found | LOW | Agent generates Marp markdown directly (fallback) |
| Invalid JSON input | MEDIUM | Script exits 1 with parse error — agent fixes JSON and retries |
| Marp not installed | LOW | Script outputs plain .md — user installs Marp CLI separately |
| Too many slides (>30) | MEDIUM | Agent should split into multiple decks or summarize |
| System/architecture/flow/sequence/state/ER/swimlane diagrams | MEDIUM | Editorial HTML/SVG diagrams → diagram. For an editorial slide graphic: diagram with size=slide-16x9, then embed the HTML or a screenshot — do NOT replace the Marp type: diagram fence (that stays Mermaid for build-deck.js) |
Constraints
- Output MUST be valid Marp markdown (parseable by
@marp-team/marp-cli) - DO NOT embed build-deck.js source in this skill — call it via
{scripts_dir} - DO NOT require Marp installation — output is standard markdown that Marp can consume
- Keep slide count reasonable (5-15 for demos, 10-25 for talks)
- Always include speaker notes for non-trivial slides
Returns
| Artifact | Format | Location |
|---|---|---|
| Slide schema | JSON | slides.json (temporary) |
| Presentation deck | Marp Markdown | deck.md or user-specified path |
Done When
- Presentation type identified (demo/sprint/talk/tutorial/pitch)
- JSON schema generated with correct slide types
- build-deck.js executed (or fallback markdown generated)
- Output file path presented to user
- Preview/export commands provided
Cost Profile
~500-1500 tokens input, ~300-800 tokens output. Sonnet for quality copy and structure.
Files (rune)
-
scripts
-
build-deck.js 3.9 KB
Loading…
-
-
SKILL.md 5.3 KB
--- name: slides description: "Generate Marp-compatible slide decks from a structured JSON schema. Use when the user asks for slides, a presentation, a demo deck, sprint review slides, or a tech talk. Converts project context into presentations for talks, demos, and tutorials." metadata: author: runedev version: "0.1.0" layer: L3 model: sonnet group: media tools: "Read, Write, Bash" --- # slides ## Purpose Generates structured slide decks as Marp-compatible markdown. The agent analyzes context (feature, sprint, tutorial) and produces a JSON slide schema, then calls `build-deck.js` to convert it to presentation-ready markdown. The script standardizes output format — preventing agent freestyle errors when context runs low. ## Triggers - User says "create slides", "make presentation", "demo deck", "sprint review slides", "tech talk" - `/rune slides` — manual invocation - Called by other skills needing presentation output ## Called By (inbound) - `marketing` (L2): launch presentations, product demos - `video-creator` (L3): slide-based video storyboards - User: direct invocation ## Calls (outbound) None — pure L3 utility. ## Executable Instructions ### Step 1: Analyze Context Determine the presentation type from the user's request: | Context | Template | Typical Slides | |---------|----------|---------------| | Feature demo | Demo walkthrough | Problem → Solution → Architecture → Live demo → Next steps | | Sprint review | Sprint summary | Goals → Completed → Metrics → Blockers → Next sprint | | Tech talk | Teaching format | Hook → Concept → Deep dive → Code examples → Takeaways | | Tutorial | Step-by-step | Intro → Prerequisites → Step 1-N → Summary → Resources | | Pitch | Persuasion | Problem → Market → Solution → Traction → Ask | ### Step 2: Generate JSON Schema Create a JSON file following this schema: ```json { "title": "Presentation Title", "author": "Author Name (optional)", "theme": "default|gaia|uncover", "slides": [ { "type": "title|content|code|diagram|image|quote|section", "heading": "Slide Heading", "body": "Markdown body text", "notes": "Speaker notes (optional)", "code": { "lang": "javascript", "source": "console.log('hi')" }, "diagram": "graph LR; A-->B" } ] } ``` **Slide types:** - `title` — opening slide with `# heading` - `content` — standard slide with `## heading` + body - `code` — slide with syntax-highlighted code block - `diagram` — slide with Mermaid diagram (stays a Mermaid fence for Marp; do NOT replace with a `diagram`-generated HTML here) - `image` — slide with image reference in body - `quote` — slide with blockquote formatting - `section` — section divider with `# heading` Save the JSON to a temporary file (e.g., `slides.json`). ### Step 3: Build Deck Execute the build script: ```bash node {scripts_dir}/build-deck.js --input slides.json --output deck.md ``` The script outputs Marp-compatible markdown with: - Marp frontmatter (`marp: true`, theme) - Slide separators (`---`) - Speaker notes as HTML comments - Code blocks with language hints - Mermaid diagram blocks ### Step 4: Present Result Show the user: 1. The generated `deck.md` file path 2. How to preview: `npx @marp-team/marp-cli deck.md --preview` (or any Marp viewer) 3. How to export PDF: `npx @marp-team/marp-cli deck.md --pdf` **Fallback**: If `{scripts_dir}/build-deck.js` is unavailable, generate the Marp markdown directly — the script is an optimization, not a hard dependency. ## Output Format ```markdown --- marp: true theme: default --- # Presentation Title Author Name --- ## Slide Heading Slide body content <!-- notes: Speaker notes here --> ``` ## Sharp Edges | Failure Mode | Severity | Mitigation | |---|---|---| | build-deck.js not found | LOW | Agent generates Marp markdown directly (fallback) | | Invalid JSON input | MEDIUM | Script exits 1 with parse error — agent fixes JSON and retries | | Marp not installed | LOW | Script outputs plain .md — user installs Marp CLI separately | | Too many slides (>30) | MEDIUM | Agent should split into multiple decks or summarize | | System/architecture/flow/sequence/state/ER/swimlane diagrams | MEDIUM | Editorial HTML/SVG diagrams → `diagram`. For an editorial slide graphic: `diagram` with `size=slide-16x9`, then embed the HTML or a screenshot — do NOT replace the Marp `type: diagram` fence (that stays Mermaid for `build-deck.js`) | ## Constraints 1. Output MUST be valid Marp markdown (parseable by `@marp-team/marp-cli`) 2. DO NOT embed build-deck.js source in this skill — call it via `{scripts_dir}` 3. DO NOT require Marp installation — output is standard markdown that Marp can consume 4. Keep slide count reasonable (5-15 for demos, 10-25 for talks) 5. Always include speaker notes for non-trivial slides ## Returns | Artifact | Format | Location | |----------|--------|----------| | Slide schema | JSON | `slides.json` (temporary) | | Presentation deck | Marp Markdown | `deck.md` or user-specified path | ## Done When - Presentation type identified (demo/sprint/talk/tutorial/pitch) - JSON schema generated with correct slide types - build-deck.js executed (or fallback markdown generated) - Output file path presented to user - Preview/export commands provided ## Cost Profile ~500-1500 tokens input, ~300-800 tokens output. Sonnet for quality copy and structure.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.