Pptx deck context

Multi-harness agentic plugin marketplace for Claude Code, Codex CLI, Cursor, OpenCode, GitHub Copilot, and Gemini CLI

Install

npx -y skills add wshobson/agents --skill pptx-deck-context

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Use when preparing the narrative, sources, and design context for a new editable PPTX deck.

1.6 KB, as published. Nobody here has run it

Prepare the deck before coordinates or PPTX objects are authored. This skill owns the business narrative, source lineage, and design lock.

Confirm audience, decision, slide count, language, sources, and brand requirements.
Use the user-selected narrative framework. If none is specified, offer mckinsey, scqa, pyramid, mece, action-title, assertion-evidence, exec-summary-first, or custom; do not choose silently.
Assign stable source IDs and plan a source_ref for every metric, quotation, chart value, and factual claim.
Choose a documented design direction. Prefer a user brand guide, then read-only reference-deck evidence, then a reusable profile from references/design-profiles.md.
Record the framework, assumptions, source manifest, palette, typography, spacing, and signature elements in summary before authoring slides.

One slide should communicate one message, with an action-style title where the framework calls for it.
Treat design references as design evidence, not content or asset sources.
Do not copy external fonts, images, icons, or logos without recorded licensing evidence.
Translate design signals into explicit fills, typography, spacing, and bboxes; do not rely on an automatic layout engine.
Keep long source material concise. Ask for a summary or decision-relevant excerpt instead of turning a deck spec into a document dump.

See references/design-profiles.md for reusable profile guidance.