pptx-deck-context
Use when preparing the narrative, sources, and design context for a new editable PPTX deck.
Install
npx skills add https://github.com/wshobson/agents/tree/main/plugins/pptx-deck-creation/skills/pptx-deck-context
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
git clone https://github.com/wshobson/agents.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
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
- 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, orcustom; do not choose silently. - Assign stable source IDs and plan a
source_reffor 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
summarybefore 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.
Files (agents)
-
references
-
design-profiles.md 1.1 KB
Loading…
-
-
SKILL.md 1.6 KB
--- name: pptx-deck-context description: "Use when preparing the narrative, sources, and design context for a new editable PPTX deck." --- # 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.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.