slides
starsforks
How to install slides?
rune-kit/rune/slides
$npx -y skills add Rune-kit/rune --skill slidesGenerate Marp-compatible slide decks from structured JSON schema. Converts context into presentations for tech talks, sprint demos, and tutorials.
SKILL.md
| 1 | # slides |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | 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. |
| 6 | |
| 7 | ## Triggers |
| 8 | |
| 9 | - User says "create slides", "make presentation", "demo deck", "sprint review slides", "tech talk" |
| 10 | - `/rune slides` — manual invocation |
| 11 | - Called by other skills needing presentation output |
| 12 | |
| 13 | ## Called By (inbound) |
| 14 | |
| 15 | - `marketing` (L2): launch presentations, product demos |
| 16 | - `video-creator` (L3): slide-based video storyboards |
| 17 | - User: direct invocation |
| 18 | |
| 19 | ## Calls (outbound) |
| 20 | |
| 21 | None — pure L3 utility. |
| 22 | |
| 23 | ## Executable Instructions |
| 24 | |
| 25 | ### Step 1: Analyze Context |
| 26 | |
| 27 | Determine the presentation type from the user's request: |
| 28 | |
| 29 | | Context | Template | Typical Slides | |
| 30 | |---------|----------|---------------| |
| 31 | | Feature demo | Demo walkthrough | Problem → Solution → Architecture → Live demo → Next steps | |
| 32 | | Sprint review | Sprint summary | Goals → Completed → Metrics → Blockers → Next sprint | |
| 33 | | Tech talk | Teaching format | Hook → Concept → Deep dive → Code examples → Takeaways | |
| 34 | | Tutorial | Step-by-step | Intro → Prerequisites → Step 1-N → Summary → Resources | |
| 35 | | Pitch | Persuasion | Problem → Market → Solution → Traction → Ask | |
| 36 | |
| 37 | ### Step 2: Generate JSON Schema |
| 38 | |
| 39 | Create a JSON file following this schema: |
| 40 | |
| 41 | ```json |
| 42 | { |
| 43 | "title": "Presentation Title", |
| 44 | "author": "Author Name (optional)", |
| 45 | "theme": "default|gaia|uncover", |
| 46 | "slides": [ |
| 47 | { |
| 48 | "type": "title|content|code|diagram|image|quote|section", |
| 49 | "heading": "Slide Heading", |
| 50 | "body": "Markdown body text", |
| 51 | "notes": "Speaker notes (optional)", |
| 52 | "code": { "lang": "javascript", "source": "console.log('hi')" }, |
| 53 | "diagram": "graph LR; A-->B" |
| 54 | } |
| 55 | ] |
| 56 | } |
| 57 | ``` |
| 58 | |
| 59 | **Slide types:** |
| 60 | - `title` — opening slide with `# heading` |
| 61 | - `content` — standard slide with `## heading` + body |
| 62 | - `code` — slide with syntax-highlighted code block |
| 63 | - `diagram` — slide with Mermaid diagram |
| 64 | - `image` — slide with image reference in body |
| 65 | - `quote` — slide with blockquote formatting |
| 66 | - `section` — section divider with `# heading` |
| 67 | |
| 68 | Save the JSON to a temporary file (e.g., `slides.json`). |
| 69 | |
| 70 | ### Step 3: Build Deck |
| 71 | |
| 72 | Execute the build script: |
| 73 | |
| 74 | ```bash |
| 75 | node {scripts_dir}/build-deck.js --input slides.json --output deck.md |
| 76 | ``` |
| 77 | |
| 78 | The script outputs Marp-compatible markdown with: |
| 79 | - Marp frontmatter (`marp: true`, theme) |
| 80 | - Slide separators (`---`) |
| 81 | - Speaker notes as HTML comments |
| 82 | - Code blocks with language hints |
| 83 | - Mermaid diagram blocks |
| 84 | |
| 85 | ### Step 4: Present Result |
| 86 | |
| 87 | Show the user: |
| 88 | 1. The generated `deck.md` file path |
| 89 | 2. How to preview: `npx @marp-team/marp-cli deck.md --preview` (or any Marp viewer) |
| 90 | 3. How to export PDF: `npx @marp-team/marp-cli deck.md --pdf` |
| 91 | |
| 92 | **Fallback**: If `{scripts_dir}/build-deck.js` is unavailable, generate the Marp markdown directly — the script is an optimization, not a hard dependency. |
| 93 | |
| 94 | ## Output Format |
| 95 | |
| 96 | ```markdown |
| 97 | --- |
| 98 | marp: true |
| 99 | theme: default |
| 100 | --- |
| 101 | |
| 102 | # Presentation Title |
| 103 | |
| 104 | Author Name |
| 105 | |
| 106 | --- |
| 107 | |
| 108 | ## Slide Heading |
| 109 | |
| 110 | Slide body content |
| 111 | |
| 112 | <!-- notes: Speaker notes here --> |
| 113 | ``` |
| 114 | |
| 115 | ## Sharp Edges |
| 116 | |
| 117 | | Failure Mode | Severity | Mitigation | |
| 118 | |---|---|---| |
| 119 | | build-deck.js not found | LOW | Agent generates Marp markdown directly (fallback) | |
| 120 | | Invalid JSON input | MEDIUM | Script exits 1 with parse error — agent fixes JSON and retries | |
| 121 | | Marp not installed | LOW | Script outputs plain .md — user installs Marp CLI separately | |
| 122 | | Too many slides (>30) | MEDIUM | Agent should split into multiple decks or summarize | |
| 123 | |
| 124 | ## Constraints |
| 125 | |
| 126 | 1. Output MUST be valid Marp markdown (parseable by `@marp-team/marp-cli`) |
| 127 | 2. DO NOT embed build-deck.js source in this skill — call it via `{scripts_dir}` |
| 128 | 3. DO NOT require Marp installation — output is standard markdown that Marp can consume |
| 129 | 4. Keep slide count reasonable (5-15 for demos, 10-25 for talks) |
| 130 | 5. Always include speaker notes for non-trivial slides |
| 131 | |
| 132 | ## Returns |
| 133 | |
| 134 | | Artifact | Format | Location | |
| 135 | |----------|--------|----------| |
| 136 | | Slide schema | JSON | `slides.json` (temporary) | |
| 137 | | Presentation deck | Marp Markdown | `deck.md` or user-specified path | |
| 138 | |
| 139 | ## Done When |
| 140 | |
| 141 | - Presentation type identified (demo/sprint/talk/tutorial/pitch) |
| 142 | - JSON schema generated with correct slide types |
| 143 | - build-deck.js executed (or fallback markdown generated) |
| 144 | - Output file path presented to user |
| 145 | - Preview/export commands provided |
| 146 | |
| 147 | ## Cost Profile |
| 148 | |
| 149 | ~500-1500 tokens input, ~300-800 tokens output. Sonnet for quality copy and structure. |
People who liked this also viewed
6 picksType
- ai-video-generationinference.sh Agent skills for using our API to give your agents access to hundreds of apps and other agentsSkillsJul 2026
- imagegen-frontend-webElite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing pageSkillsJul 2026
- hyperframes-mediaWrite HTML. Render video. Built for agents.SkillsJul 2026
- media-useAgent Media OS, the single skill for every media need in a HyperFrames project. Resolve BGM, SFX, image, icon, brand logo, voice, color grade, or LUT into a frozen local file or paste-ready block + leSkillsJul 2026
- general-videoAuthor or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, staticSkillsJul 2026
- product-launch-videoTurn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market,SkillsJul 2026
