Use when preparing the narrative, sources, and design context for a new editable PPTX deck.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add thedixitjain/the-mega-skill-library --skill pptx-deck-context --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pptx Deck Context?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/thedixitjain-pptx-deck-context)More formats (shields.io, HTML) on the badges page.
---
name: pptx-deck-context
description: "Use when preparing the narrative, sources, and design context for a new editable PPTX deck."
category: media-and-creative
source_repo: wshobson/agents
source_path: "plugins/pptx-deck-creation/skills/pptx-deck-context/SKILL.md"
source_url: https://github.com/wshobson/agents/blob/HEAD/plugins/pptx-deck-creation/skills/pptx-deck-context/SKILL.md
---
# PPTX Deck Context
Prepare the deck before coordinates or PPTX objects are authored. This skill owns the business narrative, source lineage, and design lock.
## Decision sequence
1. Confirm audience, decision, slide count, language, sources, and brand requirements.
2. 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.
3. Assign stable source IDs and plan a `source_ref` for every metric, quotation, chart value, and factual claim.
4. 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`.
5. Record the framework, assumptions, source manifest, palette, typography, spacing, and signature elements in `summary` before authoring slides.
## Rules
- 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.
---
**Source:** [`wshobson/agents`](https://github.com/wshobson/agents) → `plugins/pptx-deck-creation/skills/pptx-deck-context/SKILL.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!