powerpoint-deck-builder
Skill0 starsChanged 3 months agoMITView on GitHub
Plan, create, revise, and verify native editable PowerPoint presentations with source-aware content, reusable layouts, speaker notes, and rendered visual QA. Use when the deliverable must be an editable .pptx or must reuse an existing PowerPoint template.
In this repository3 other files it gives its agents.
- html-deck-builderSkill
- magazine-web-deckSkill
- presentationSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 23
Use the available PowerPoint-capable runtime.
- Distinctive: line 24
Keep text, charts, tables, and core shapes editable.
- Distinctive: line 28
Do not treat successful file generation as visual approval, and do not claim editable output when important content was flattened without …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
PowerPoint Deck Builder
Designed, integrated, independently refactored, and continuously maintained by TIKAZ.
TIKAZ Edition
- Type: original tool-agnostic workflow; no third-party templates, fonts, images, or scripts are bundled.
- TIKAZ contribution: narrative-to-page contract, editability gate, template fidelity rules, render/overflow QA, and delivery evidence.
Inputs
Accept a brief or source files, audience, duration, aspect ratio, required template, editability, notes, charts, language, and delivery constraints.
Workflow
- Determine audience, talk length, aspect ratio, required template, editability, notes, charts, and delivery constraints.
- Convert the narrative into page contracts with one claim and one visual job per slide.
- Use the available PowerPoint-capable runtime; inspect a provided template before authoring and preserve its layout rules.
- Keep text, charts, tables, and core shapes editable. Record the license and source for external media.
- Render the deck to images and inspect representative and dense slides; iterate on overflow, collisions, hierarchy, contrast, and repetition.
- Reopen or inspect the final
.pptx, confirm slide count and notes, and report the exact artifact plus verification evidence.
Do not treat successful file generation as visual approval, and do not claim editable output when important content was flattened without disclosure.
Output contract
Return the editable .pptx, narrative and page contracts, template or font substitutions, source and license ledger, speaker notes when requested, rendered slide evidence, and final file inspection results.
Validation and fallback
Render every slide, inspect dense and representative slides, verify overflow and collisions, reopen the final deck, and confirm slide count, notes, and editability. If the required template, font, or renderer is unavailable, disclose the substitution or stop before claiming fidelity.
Example
Use powerpoint-deck-builder to create an editable 16:9 deck from this brief, preserve the supplied template, render every slide, and report substitutions.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.