zz-deck

Convert existing prose documents into argument-driven HTML slide decks on a fixed visual system.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/zhixuan312/zz-stack --skill zz-deck-zhixuan312
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zz-deck
Source: https://github.com/zhixuan312/zz-stack/tree/main/skills/zz-deck
Command: npx skills add https://github.com/zhixuan312/zz-stack --skill zz-deck-zhixuan312

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec, report, changelog, or thread into a slide deck usually produces a table of contents with a background — one slide per heading, bullets everywhere. This Skill forces the deck to be an argument: a stated conclusion, the claims that carry it, and one deliberate visual composition per claim, rendered on a fixed house design system. ## Core Features & Use Cases - Argument-first structure: Derives a one-sentence conclusion and 3–7 ordered claims from the source before any layout decision, with every slide title written as a declarative assertion rather than a label. - Composition routing: Maps each claim's evidence to a composition family (lane, graph, band, matrix, plot, chart, statement, table) instead of defaulting to bullet lists. - Deterministic HTML output: Scaffolds a deck from the bundled deck-chassis.html asset, fills one slide per exact-string edit, and writes a single self-contained file to decks/YYYY-MM-DD-<slug>.html. - Built-in self-QA: Ships a ?qa panel plus manual checks covering overflow, contrast, figure accessibility, title quality, and print/PDF fidelity. - Use Case: Paste a design doc and ask for a projected deck for an engineering review; the Skill reads the source, extracts the argument, chooses compositions, and emits a finished HTML deck you open in a browser. ## Quick Start Turn the attached design doc into a 10-slide projected deck for an engineering audience using the zz-deck skill.

Frequently Asked Questions about zz-deck

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a document into a slide deck with AI?▼

Provide the source document and optionally a slide count and audience. The Skill reads the source fully, derives a conclusion and 3–7 claims, picks one composition per claim, and writes a self-contained HTML deck to decks/YYYY-MM-DD-<slug>.html.

How to make slide titles that are assertions instead of labels?▼

Write each title as a declarative sentence with a finite verb, two lines maximum, that answers the implicit so-what question. If the title could sit unchanged in a different document, it is a label and must be rewritten.

What output format does the deck generator produce?▼

It produces a single offline HTML file built on the bundled deck-chassis.html asset, containing the style layer, behaviour scripts, a JSON slide manifest, and one section per slide. No platform tools or external services are called.

Does the deck skill work for printed or PDF slides?▼

Yes, but the Skill instructs checking the printed PDF rather than the on-screen preview, since print re-lays out each slide and can silently drop content. It recommends pdftotext character counts and pdftoppm rasterisation to verify pages.

Why does the Agent metadata QA row fail on a real deck?▼

That failure is expected and correct. The row requires data-use, data-choose, data-limits, and data-tags attributes, which are teaching metadata for the guidebook's reference slides, not fields a content slide should carry.

When should I not use bullet lists on slides?▼

Bullets are only valid for genuine peers such as options or checklists. Evidence should be shown through a composition — chart, diagram, table, or statement — because bullet lists flatten hierarchy and hide relationships between items.