deck-author
Skill0 starsChanged 4 days agoMITView on GitHub
Transform a topic, outline, Markdown, or speaker notes into a narrative bento deck using an extracted PowerPoint theme.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mhashim6/telepromptertheir own version, first seen Jun 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mhashim6/teleprompter★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- deck-buildSkill
- deck-qaSkill
- faviconSkill
- site-buildSkill
- theme-extractSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Before creating slides, establish audience, purpose, key message, duration, and source material.
- Distinctive: line 10
Use one clear idea per slide.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Author the slide narrative
Before creating slides, establish audience, purpose, key message, duration, and source material. For supplied Markdown, preserve its title and section order unless the user asks for a restructure.
Use one clear idea per slide. Prefer a strong headline, short explanation, concrete examples, and meaningful visual structures over bullet-heavy slides. Use charts only when source data supports them; never invent metrics. Put speaker notes on slides only when the user supplied or requested them.
Build from the reviewed theme JSON:
node scripts/deck-build.mjs --theme theme.json --content outline.md --out dist/deck.bento.htmlLet the builder handle the theme's fonts: it embeds licence-permitted files and otherwise keeps a metric-compatible or system stack. Use <!-- layout: section --> (or another role or layout name) under a heading when a slide should use a specific source layout. Make slide IDs and element IDs deterministic, maintain accessible contrast, and leave reasonable margins.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

