Presentation Skill
Generate and QA-check editable PowerPoint decks from structured outlines instead of fragile one-off python-pptx scripts.
Overview
Presentation Skill is an agent skill most often used in Launch (also Validate, Build) that builds, edits, and QA-checks editable `.pptx` slide decks from `outline.json` and repo scripts—not hand-written deck code.
Install
npx skills add https://github.com/sirilsengolraj-source/presentation-skill --skill presentation-skillWhat is this skill?
- Authors `outline.json` and runs repo-native scripts—no ad hoc inline `python-pptx` or `pptxgenjs` deck code
- Compatibility aliases: `powerpoint-deck-builder`, `pptx-skill`; searchable as PowerPoint/PPTX slide deck generator
- Mandatory QA for deliverable decks, including render-free QA when LibreOffice is unavailable
- Fixes source (`outline.json`, plans, assets, renderer)—not mutated `.pptx` artifacts
- Scaffolds fresh workspaces per new topic instead of cloning another deck’s structure
- 5 non-negotiable deck rules in SKILL.md (outline+scripts, no mid-run reinstall, mandatory QA, fix sources not `.pptx`, f
Adoption & trust: 2 installs on skills.sh; 11 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+200% hot-view momentum).
What problem does it solve?
You need a professional slide deck but ad-hoc PowerPoint libraries and one-off scripts produce misaligned slides, skipped QA, and brittle `.pptx` files you cannot safely iterate.
Who is it for?
Solo builders shipping pitch decks, launch narratives, or reusable presentation workspaces with agent-planned structure and script-backed rendering.
Skip if: Teams that only need a Google Slides copy-paste or a single static image export with no outline-driven iteration or QA pipeline.
When should I use this skill?
User asks to build, edit, verify, or iterate polished PowerPoint `.pptx` presentations, slide decks, or decks from `outline.json` or saved workspaces.
What do I get? / Deliverables
You get a verified, editable `.pptx` deck driven by `outline.json` and workspace assets, with alignment and overflow checks completed before you share or present.
- Verified `.pptx` deck
- Authoritative `outline.json` and workspace assets
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch is the canonical shelf because polished slide decks are most often shipped as distribution assets—pitches, demos, and GTM narratives—not as runtime code. Distribution covers outward-facing decks (sales, investor, launch narratives) that this skill optimizes for alignment, overflow checks, and deliverable `.pptx` quality.
Where it fits
Turn a scoped MVP narrative into a pitch outline.json before you commit engineering weeks.
Convert technical architecture notes into a polished internal deck for collaborators.
Ship a launch-week demo deck with alignment QA and source-backed assets.
Refresh webinar or content slides in a saved workspace without cloning an old deck’s structure.
How it compares
Use instead of prompting the agent to write inline `python-pptx`/`pptxgenjs` for every deck—this skill enforces outline-first generation and mandatory QA.
Common Questions / FAQ
Who is presentation-skill for?
Solo and indie builders using Codex or ChatGPT-style agents who need editable PowerPoint `.pptx` files with design alignment and verification, not one-off script hacks.
When should I use presentation-skill?
Use it during Validate when shaping an investor pitch outline, during Build when packaging product docs as slides, and during Launch when producing distribution or demo decks from `outline.json`.
Is presentation-skill safe to install?
Review the Security Audits panel on this Prism page and inspect the repo scripts your agent will execute; do not assume pass/fail counts from this listing alone.
SKILL.md
READMESKILL.md - Presentation Skill
# Presentation Skill Repo-native PowerPoint skill for editable, aligned, QA-checked `.pptx` decks. The model plans the story and visual strategy; scripts handle fragile rendering, staging, and verification. Call this skill as `presentation-skill`. Compatibility aliases: `powerpoint-deck-builder` and `pptx-skill`. Search aliases: PowerPoint skill, PPTX skill, presentation skill, slide deck generator, slides generator, deck builder, presentation generator. ## Non-Negotiables - Do not write ad hoc inline `python-pptx` or `pptxgenjs` deck code. Author `outline.json` and run repo scripts. - Do not reinstall dependencies during deck generation. Missing dependency: report it and stop. - Do not skip QA for a deliverable deck. Use render-free QA when LibreOffice is unavailable. - Fix source files (`outline.json`, plans, assets, renderer code), not mutated `.pptx` artifacts. - For a new topic, scaffold fresh. Do not clone another deck's structure as a house style. ## First Files To Read - `DESIGN.md`: compact design contract, colors, hierarchy, alignment rules, generated-image disclosure. - `references/outline_schema.md`: accepted `outline.json` fields and variants. - `references/planning_schema.md`: `design_brief.json`, `content_plan.json`, and `evidence_plan.json` shape. - `references/deck_workspace_mode.md`: saved-workspace workflow. - `references/agent_picker.md`: concise picker guidance for agents and people. - `references/visual_qa_prompt.md`: visual-review packet and fresh-eyes inspection prompt. - `references/editing.md`: only when editing an existing deck. - `references/pptxgenjs.md`: only when editing JS renderer/templates. ## Workflow ### Quick Deck Use for one-shot 5-10 slide decks. ```bash node scripts/build_deck_pptxgenjs.js \ --outline outline.json \ --output out.pptx \ --style-preset <preset> python3 scripts/qa_gate.py \ --input out.pptx \ --outdir /tmp/pptx-qa \ --style-preset <preset> \ --strict-geometry \ --skip-render \ --fail-on-design-warnings ``` ### Saved Workspace Use when the deck will be extended, audited, or rebuilt later. ```bash python3 scripts/init_deck_workspace.py \ --workspace decks/my-deck \ --title "My Deck" \ --style-preset <preset> # edit design_brief.json, content_plan.json, evidence_plan.json, # asset_plan.json, notes.md, outline.json python3 scripts/build_workspace.py --workspace decks/my-deck --qa --overwrite ``` Add `--visual-review` once the source text is stable and rendered-slide judgment matters. It creates `build/qa/visual_review/visual_review.md` plus a contact sheet for fast source-level iteration. For public or research topics where credible images should be part of the deck, use source-backed visual planning: ```bash python3 scripts/build_workspace.py --workspace decks/my-deck \ --plan-research-assets --allow-network-assets --qa --overwrite ``` This fills a stub `asset_plan.json` with Wikimedia Commons queries, updates selected slides to use staged `image:<name>` aliases, writes `assets/attribution.csv`, and lets the renderer append an Image Sources slide. Workspace source files: - `design_brief.json`: audience posture, cover concept, structure strategy, grid policy, and card/container rules. - `content_plan.json`: thesis, audience, slide roles, visual strategy. - `evidence_plan.json`: sourced facts, metrics, claims, chart candidates. - `asset_plan.json`: source-backed images, charts, icons, optiona