SkillAgentSearch skills...

slide-deck

When you want to draft, update, convert, or export a slide deck for a React/Next.js slide system (${SLIDE_DECK_REPO:-$HOME/code/your-slide-deck-site}/src/app/slides/).

Install / Use

npx skills add coreyhaines31/makerskills --skill slide-deck

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Universal

Our assessment of slide-deck

slide-deck scores 92/100 on our quality scale, 923rd of 4,705 Development & Engineering skills we index (top 20%).

Its SKILL.md is 17 KB long, well organised into 18 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

It has 824 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 31 days ago, so slide-deck is actively maintained.
  • Our last check on 2026-11-18 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

slide-deck compared with similar skills

All 4 of these similar skills score higher than slide-deck; compare them before choosing.

SkillScoreStarsUpdatedFormat
slide-deck (this skill)by coreyhaines319282431d agoSKILL.md
taste-skillby Leonxlnx100120.0ktodayCLAUDE.md
hyperframesby heygen-com10088.2ktodayCLAUDE.md
rufloby ruvnet10082.3ktodayCLAUDE.md
headroomby headroomlabs-ai10080.5ktodayCLAUDE.md

Frequently asked questions

How do I install slide-deck?
Run npx skills add coreyhaines31/makerskills --skill slide-deck. The install tabs above show the steps for each supported agent.
Which AI agents does slide-deck work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is slide-deck safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is slide-deck still maintained?
The repository was last updated 31 days ago, so slide-deck is actively maintained.

name: slide-deck description: When you want to draft, update, convert, or export a slide deck for a React/Next.js slide system (${SLIDE_DECK_REPO:-$HOME/code/your-slide-deck-site}/src/app/slides/). Writes TypeScript Slide[] arrays using your primitives (Eyebrow, Heading, Accent, Body, BulletList, Divider, TwoCol, GradientText), 12 cycling brand gradients, optional sections for "where am I" context, and speaker notes. Inspired by zarazhangrui/frontend-slides — "show, don't tell" applied to narrative (presents 3 angles, you pick) plus density modes (speaker-led vs reading-first). Four modes — new (draft from brief), update (modify existing, with overflow guards), ppt (convert legacy PPTX → React deck), export (Playwright snapshot existing React deck to standalone HTML, PDF, or Vercel URL — keeps brand). Triggers on "/slide-deck," "/slides new," "/slides export," "/slides update," "/slides ppt," "draft a deck," "deck for [topic]," "talk on [topic]," "keynote on [topic]," "internal deck for [audience]," "convert this pptx," "export this deck." metadata: version: 0.2.0

/slide-deck — Draft, update, convert, and export branded React decks

Authors React/TypeScript decks for ${SLIDE_DECK_REPO:-$HOME/code/your-slide-deck-site}/src/app/slides/<slug>/page.tsx using the user's slide system. Branded output (no separate HTML pipeline) — when portable HTML/PDF is needed, export mode snapshots the rendered React deck via Playwright so the output is brand-perfect.

Modes (pick one before Step 1)

| Mode | Invocation | Goal | |---|---|---| | new | /slide-deck new <topic> (default) | Draft a new deck from a brief | | update | /slide-deck update <slug> | Modify an existing deck (with overflow guards) | | ppt | /slide-deck ppt <path-to-pptx> | Convert a legacy PPTX into a React deck | | export | /slide-deck export <slug> [html\|pdf\|vercel] | Snapshot a deck to HTML, PDF, or Vercel URL |

For update, ppt, and export, skip to the corresponding mode section below. For new, continue through Steps 1–8.


Step 1 — Capture the brief (ask all at once)

Ask in one structured message. Don't round-trip on each.

  1. Topic / title — what's the deck about?
  2. Audience — who's in the room? (technical / executive / mixed / clients) Push for specificity: "founders" is too broad; "B2B SaaS founders at MicroConf" is workable.
  3. Length — rough slide count: 5–10 (lightning / short internal) / 10–15 (short keynote, pitch) / 20–25 (keynote) / 30+ (workshop — uncommon for branded decks).
  4. Density — speaker-led (1 idea/slide, big type, lots of breathing room, more slides if needed) or reading-first (4–6 bullets/slide, structured grids, self-contained for async review).
  5. CTA — what should the audience do/think/feel after?
  6. Slug — kebab-case (e.g., marketing-like-an-engineer).
  7. Content state — all content ready / rough notes / topic only.

Remember density — it affects slide count, copy length per slide, and which primitives to favor. See references/narrative-and-voice.md for the density-specific rules.

Step 2 — Three narrative angles

Riff on zarazhangrui/frontend-slides' "show, don't tell" — but applied to story, not visuals (your visual system is fixed).

Pitch 3 angles in 1–2 sentences each:

  • Safe — most likely to land. Conventional structure for the audience.
  • Bold — contrarian or counterintuitive frame. Higher upside, slight risk.
  • Wildcard — unexpected structure (story-first, single-question deck, anti-thesis, etc.).

The user picks one. If they reject all three, propose three more — don't force a path.

Step 3 — Outline

For the chosen angle:

  1. Sections — propose 3–7 named sections (e.g., Title, Hook, Problem, Framework, Examples, Close). The default 3-act structure is OPTIONAL; only use it if the user wants it or the deck is a keynote-length talk that benefits from one.
  2. Slide titles within each section
  3. One-line takeaway per slide

Total slide count should match the duration estimate from Step 1.

Show the outline as a table. the user edits / approves before expand.

Step 4 — Expand to slide content

For each slide, write the full content using the user's primitives. Reference references/system.md for the primitive vocabulary and references/narrative-and-voice.md for hook patterns and voice rules.

Slide types and which primitives fit:

| Slide type | Primitives | Pattern | |---|---|---| | Title | Eyebrow + <h1> with <Accent> keyword | First slide, sets brand and topic | | Hook | Heading + Body | A take, story open, contrarian frame, or specific stat | | Section divider | Eyebrow + Heading (centered, large) | Clean break between sections | | Framework | Heading + BulletList or custom layout | The thing the user's teaching | | Two-column | TwoCol | Comparison, before/after, problem/solution | | Quote / pull-quote | Body (large) | Authority or audience-recognition moment | | Resource / link | Body + URL on its own line | Outbound (rare — the user's voice says minimize) | | Close / CTA | Heading + Body + BulletList for next steps | What the audience should do |

Voice anchors — write for the ear, not the page (see narrative-and-voice.md for full rules):

  • Decks are spoken aloud. Slide text + speaker notes both get said out loud. Write as you'd talk.
  • Read every slide out loud before saving. If you stumble, if it sounds like a press release, rewrite.
  • Contractions everywhere (don't, won't, you're, I'd). Strip them only on reading-first decks.
  • "You" — never "the audience," "users," "people."
  • Numbers said naturally ("a quarter" not "23.7%").
  • Conviction-coded, listener-perspective, short sentences, specific nouns.
  • No filler ("Today I want to talk about…") — open with a take.
  • (Reading-first density mode exception: written voice is fine since no one will speak the slides — see narrative-and-voice.md.)

Step 5 — Speaker notes

Every slide gets 3–5 notes lines. Notes are the full spoken talk — write them the way you'd actually say them, pauses and asides included. Slide text is the headline; notes are the full thought.

Notes structure:

  1. The opener — what you say when the slide comes up
  2. The point — the one idea this slide is making
  3. The supporting beat — example, data, or color
  4. The transition — how this connects to the next slide
  5. (Optional) The aside — a quip or callback

For title slides and section dividers, 2–3 notes is fine.

Step 6 — Generate files

Write to ${SLIDE_DECK_REPO:-$HOME/code/your-slide-deck-site}/src/app/slides/<slug>/:

  1. layout.tsx — Next.js layout with <title> metadata (use the deck title)
  2. page.tsx — the slide deck

Use the templates in references/template.md as the skeleton.

The <AUTHOR_HANDLE> / <AUTHOR_SITE> tokens (close-slide footer) come from ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/slide-deck/identity.yaml (keys: handle, site) if it exists. Otherwise ask the user for their handle and site once, offer to save them there, and use those. If they don't want a footer, drop the <p> entirely — never ship a deck with someone else's identity on it.

page.tsx must:

  • Have "use client" at the top
  • Import SlideDeck and Slide type from @/components/slides/slide-deck
  • Import SectionRange from @/components/slides/sections (only if using sections)
  • Import the primitives the user uses from @/components/slides/slide-primitives
  • Declare const slides: Slide[] = [...]
  • (Optional) Declare const sections: SectionRange[] = [...] with 0-indexed from/to
  • Export default a component that returns <SlideDeck slides={slides} sections={sections} />

Step 7 — Preview

After writing the files, check if your slide-deck dev server is running.

lsof -i :3000-3099 2>/dev/null | grep -E "LISTEN" | head

If a port is in use (portless-compatible — check package.json for the dev script naming):

# Suggested URL pattern
echo "Preview at: http://${SLIDE_DECK_DEV_HOST:-localhost:3000}/slides/<slug>"

If no dev server is running, tell the user:

cd ${SLIDE_DECK_REPO:-$HOME/code/your-slide-deck-site} && npm run dev
# then visit http://${SLIDE_DECK_DEV_HOST:-localhost:3000}/slides/<slug>

Don't auto-start the dev server (might disrupt other work).

Step 8 — Archive

The archive lives in ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/slide-deck/archive/ (create the directory if missing). Never write the archive inside the skill's own folder — skill installs and upgrades re-sync from source and wipe anything saved there. Migration: if this skill's folder contains an old references/decks-archive.md with user entries, move it to <archive dir>/INDEX.md first.

Append a one-liner to <archive dir>/INDEX.md (create if missing):

- 2026-06-17 — [<title>](${SLIDE_DECK_REPO:-$HOME/code/your-slide-deck-site}/src/app/slides/<slug>/page.tsx) — <audience> — <one-line angle>

This compounds — future decks can grep "what talks have I done about X" to avoid repetition and find reusable patterns.


Mode: update

Modify an existing deck without breaking it. Risks: overflowing slides, exceeding density limits, breaking the section ranges.

Before modifying, check:

  1. Read the existing page.tsx
  2. Count slides + identify the section ranges
  3. For each modification, apply the right guard:

| Change | Guard | |---|---| | Adding bullets | Max 6 per BulletList in reading-first; 3 in speaker-led. If exceeded → split into two slides. | | Adding text | If <Body> paragraph >2 sentences in speaker-led → split. >5 sentences in reading-first → split. | | Adding images | Images must fit in the 1920×1080 stage. If the slide already has heavy content, move image to its own slide. | | Adding slides | Update sections array — increment from/to for all sections after the insertion point. | | Removing slides | Decrement from/to for sections after the removal. Watch for orphaned id references. | | Rewriting a slide | Preserve the id (used for anchors). Only change content and notes. |

After modifying:

  • Re-count slides and verify section ranges sum correctly
  • Spot-check the visual in the dev server before committing

Mode: ppt

Convert a legacy PPTX (client deck, conference template) into the user's React system.

  1. Extract content via python3 and python-pptx:

    pip install python-pptx 2>/dev/null
    python3 -c "
    from pptx import Presentation
    import json, sys
    p = Presentation(sys.argv[1])
    out = []
    for i, s in enumerate(p.slides):
        title = next((sh.text for sh in s.shapes if sh.has_text_frame and sh.shapes_element.tag.endswith('}sp') == False), '')
        texts = [sh.text for sh in s.shapes if sh.has_text_frame]
        notes = s.notes_slide.notes_text_frame.text if s.has_notes_slide else ''
        out.append({'i': i, 'texts': texts, 'notes': notes})
    print(json.dumps(out, indent=2))
    " "<path-to-pptx>"
    

    See references/ppt-conversion.md for the full extraction + mapping recipe.

  2. Show the user the extracted summary — slide titles, content excerpts, image count. Confirm before proceeding.

  3. Map to React primitives:

    • First slide → title pattern (Eyebrow + h1 + Accent)
    • Content slides with bullets → Heading + BulletList
    • Comparison slides → TwoCol
    • Section breaks (title-only slides in PPTX) → section divider pattern
    • Speaker notes from PPTX → notes array on each slide
  4. Images — copy referenced images from PPTX assets to ${SLIDE_DECK_REPO:-$HOME/code/your-slide-deck-site}/public/slide-assets/<slug>/, reference them in slides via <img src="/slide-assets/<slug>/<filename>" /> inside the content.

  5. Write page.tsx + layout.tsx per the new-deck flow (Step 6).

  6. **Preserve the original

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars824
CategoryDevelopment
Updated1mo ago
Forks67

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions