Skip to content
Skills Library
Marketing & content · Building & coding

deck

/deck

Build a presentation as one self-contained HTML file (1920×1080 slides, keyboard navigation, builds, speaker notes, presenter view, print to PDF) on the deckfile engine, with no build step or dependencies. Use when the user asks for a presentation, slide deck, slides, a talk or a keynote and wants an HTML deck, or doesn't name a format and has no slide tool of their own. Not for .pptx or Google Slides.

Repository
deckfile ↗
Licence
MIT
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build a presentation as one self-contained HTML file (1920×1080 slides, keyboard navigation, builds, speaker notes, presenter view, print to PDF) on the deckfile engine, with no build step or dependencies. Use when the user asks for a presentation, slide deck, slides, a talk or a keynote and wants an HTML deck, or doesn't name a format and has no slide tool of their own. Not for .pptx or Google Slides.

Original author description

Build a presentation as one self-contained HTML file (1920×1080 slides, keyboard navigation, builds, speaker notes, presenter view, print to PDF) on the deckfile engine, with no build step or dependencies. Use when the user asks for a presentation, slide deck, slides, a talk or a keynote and wants an HTML deck, or doesn't name a format and has no slide tool of their own. Not for .pptx or Google Slides.

How it works

  1. Workflow
  2. House rules
Original SKILL.md headings · 87 lines, 1,056 words
SKILL.md preview
---
name: deck
description: Build a presentation as one self-contained HTML file (1920×1080 slides, keyboard navigation, builds, speaker notes, presenter view, print to PDF) on the deckfile engine, with no build step or dependencies. Use when the user asks for a presentation, slide deck, slides, a talk or a keynote and wants an HTML deck, or doesn't name a format and has no slide tool of their own. Not for .pptx or Google Slides.
---

# deck

This skill produces `<slug>/index.html`: one file that opens from `file://`
with no network, apart from an optional Google Fonts stylesheet with local
fallbacks. Its engine is [deckfile](https://github.com/roaldnefs/deckfile):
vanilla JS plus plain CSS, inlined between `data-deck="engine"` tags. The deck
is easy to diff, easy to host anywhere, has a presenter view, and prints to a
PDF with one slide per page.

Bundled files:
- `assets/template.html`: the engine, the default theme, and slides that explain deckfile. **Always start from a copy of it.**
- `references/components.md`: the markup for every slide variant and component. Read it before writing slides.
- `references/theming.md`: tokens, fonts, logos and skins. Read it when the user wants a brand.

## Workflow

### 1. Brief

Collect what you need. Take what the user has already said and ask only about the gaps, in one round:
- **Topic and the one thing the audience should remember.**
- **Audience:** who they are and what they already know.
- **Length** in minutes.
- **Language** of the slides.
- **Event, date, speaker name and role** for the title and closing slides.
- **Brand:** the default theme, or colours, logo SVGs and fonts. Fonts must be openly licensed; see theming.
- **Material:** source documents, data, photos or screenshots to use.

If you can't ask (a non-interactive run) or the user says "just make it", choose sensible defaults, state them in one line, and carry on.

### 2. Outline

Before writing any HTML, propose a slide-by-slide outline. Each line gives the slide number, its variant or layout, the heading, and its point in one line. Group the lines under sections with minutes per section.

Sizing: about 1–2 minutes per content slide, plus a title, an agenda (for talks over 10 minutes), a divider per section and a closing slide. A 20-minute talk is usually 12–18 slides.

Get the user's go-ahead on the outline. Restructuring an outline is cheap; restructuring HTML is not.

### 3. Build

1. Copy `assets/template.html` to `<slug>/index.html`, where `<slug>` is a short kebab-case name for the talk. Do not overwrite an existing deck without asking.
2. Set `<html lang>` and `<title>`.
3. Delete every example `<section>` between `<div id="stage">` and its closing `</div>`. Write the new slides there, using markup from `references/components.md`. Keep `<template data-deck="layouts">` before the stage, as the edit view's **New slide** offers those layouts.
4. Brand (if any): change the tokens in `:root` of `<style data-deck="theme">` and the Google Fonts `<link>`, as described in `references/theming.md`. Deck-specific CSS goes in the last `<style>`, under `/* deck-specific */`.
5. Copy images the user supplied next to `index.html` and reference them by relative path.

**Never edit the `<style data-deck="engine">` or `<script data-deck="engine">` blocks.** They are replaced whole when the engine is updated (`npx github:roaldnefs/deckfile update <slug>/index.html`). If the engine truly can't do something, add CSS under the deck-specific heading. If behaviour is needed, add a separate small `<script>` after the engine's, and say why.

The user can also change the deck from its edit view and save it. That first save rewrites some markup the way the browser reads it (self-closed SVG tags, `<tbody>`, entities), so don't take such changes in a diff for edits of theirs. Read the file again before changing a deck they may have saved.

### 4. Speaker notes

Every section ends with `<div class="s-notes">…</div>`. Write what the speaker *says*, in their voice: the opening line, the transition into the next slide, and the one point to stress. Don't restate the slide text. Mark any line meant to be read out word for word as "verbatim".

### 5. Self-check

Before you report the deck as done, check it and fix what fails:
- [ ] Every slide is `<section class="slide …">` inside `#stage` and ends with an `s-notes` div.
- [ ] Every number, chart or quote that isn't from a source the user gave says so on the slide, in a `<p class="small">Illustrative data</p>` line. **Never present an invented figure as fact.**
- [ ] The only external URL in `<head>` is Google Fonts. There are no CDN scripts and no remote images.
- [ ] Images are relative files that exist. Nothing is base64-encoded except small SVG logos.
- [ ] Every font is openly licensed (for example SIL OFL), and no commercial face is named, even as a fallback.
- [ ] The `data-deck="engine"` blocks are unchanged from the template (`npx github:roaldnefs/deckfile update --check <slug>/index.html` exits 0).
- [ ] Nothing overflows the 1920×1080 canvas. As a rule of thumb, at most 5 bullets per slide, terminal panels of 12 lines or fewer, and headings that fit on two lines.
- [ ] The slide count fits the time slot.

If you can run a headless browser, render the deck and look at it: print it to PDF (one page per slide) or take 1920×1080 screenshots, then check for overflow, clipped text and contrast.

### 6. Hand-off

Tell the user:
- The path to the deck, and how to open it (open `index.html` in any browser).
- How to present: `→`/`Space` next, `←` back, `↓`/`↑` whole slide, `F` fullscreen, `P` print to PDF, `S` presenter view in a second window with notes and a timer, `E` edit view to change text and elements, add, duplicate, reorder and delete slides and save the file, or to suggest changes and copy them as one prompt.
- Which content is marked illustrative and needs real numbers.
- Any assumptions you made in the brief.

## House rules

- **One idea per slide.** If a slide needs two headings, it is two slides.
- **Builds are for reveals,** such as a list told point by point or a punchline. They are not decoration. Use `data-auto` for groups that should simply appear, like stat rows.
- **Show, don't list.** Prefer a stat row, terminal panel or photo over a fifth bullet.
- **Headings say the point** ("Most breaches start with a reused password"), not the topic ("Passwords").
- **Kickers are optional, and show the position** (`02 · Section name`). Dividers carry the number only.
- **Use `.dark` slides sparingly,** for section dividers and breathing moments.
- **Use `<img>` for photos, not CSS backgrounds,** because backgrounds can vanish in PDF output.
- **Test offline.** The deck must work with Wi-Fi off. That means nothing loaded from a CDN and every font stack falling back cleanly.
Files in this package (4)
  • SKILL.md 7 KB
  • assets/template.html 127 KB
  • references/components.md 6 KB
  • references/theming.md 4 KB

Versions

RepositoryScoreLicence
This page · roaldnefs/deckfile100MIT
zauberzeug/game-of-cards100MIT
zauberzeug/game-of-cards100MIT
zauberzeug/game-of-cards100MIT
octavehq/lfgtm100MIT
ramonk2o/storymaker100MIT
wookiya1364/scv-claude-code100MIT
MBGrao/deck-skill100MIT
prmvanschie/deck-skill100MIT

Database snapshot: 13.11.2026 · package version 798000514b94 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100html-deck-builder
    Build professional HTML slide presentations as single self-contained files with keyboard navigation, speaker notes, and progress tracking. Use when asked to 'build a presentation', 'create a slide deck', 'make slides', 'build a deck', 'presentation about X', 'create a…
  • 100presentation-design
    Design slide decks as HTML/CSS (custom or reveal.js): slide layouts on a fixed 16:9 canvas, presentation typography, slide charts, builds and transitions, speaker notes, and PDF export. Use for decks presented or shared from the browser; for native .pptx files use a…
  • 100slides-to-site
    Publish a Google Slides presentation on psd401.ai from just its link. Reads every slide, the speaker notes and a PDF of the deck, works out the title, date, presenters, audience and format, asks only for what the deck does not say, writes the page, opens a PR, waits for CI,…
  • 100deck-pdf
    Build a PDF presentation (one page per slide) from a topic or an outline. Use it when the user asks for a deck, slides or a presentation and wants a PDF file to share or print. If no browser is available it hands over the HTML instead.
  • 100md-slides
    Converts a markdown deck (slides separated by `---` HR boundaries or by `# ` H1 headings, with optional `<!-- notes: ... -->` presenter notes blocks) into a single-file HTML presentation with arrow-key / space / PgDn / PgUp / Home / End / P / Esc keyboard navigation, presenter…
  • 100slide-deck
    Write a slide deck as one self-contained HTML file with animation, step reveals, reduced motion and a print style sheet for PDF. Use when the user asks for a deck, slides or a presentation.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.