Development
Skill
/pptx-deck-context
Use when preparing the narrative, sources, and design context for a new editable PPTX deck.
Claude Code
$ npx -y skills add wshobson/agents --skill pptx-deck-context --agent claude-code
Codex
$ npx skills add wshobson/agents --skill pptx-deck-context -a codex -y
Cursor
$ npx skills add wshobson/agents --skill pptx-deck-context -a cursor -y
Gemini CLI
$ npx skills add wshobson/agents --skill pptx-deck-context -a gemini-cli -y
GitHub Copilot
$ npx skills add wshobson/agents --skill pptx-deck-context -a github-copilot -y
OpenCode
$ npx skills add wshobson/agents --skill pptx-deck-context -a opencode -y
Windsurf
$ npx skills add wshobson/agents --skill pptx-deck-context -a windsurf -y
SKILL.md
pptx-deck-context.SKILL.mdname: 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.
Read more
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.
Stats
42,403
Stars
4,481
Forks
Active
Maintenance
Python
Language
MIT
License
Last commit
Created
Ships withagents
Use one collection of plugins, agents, skills, and commands across Claude Code, OpenAI Codex CLI, Cursor, OpenCode, Antigravity CLI, GitHub Copilot, and Pi. A harness is the coding tool that loads and runs the components.
42k185 skills137 agents
Stars on GitHub
Momentum
- stars in total
- 42.4k
Other skills on agents.
More skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about pptx-deck-context.
- Which coding agents can use pptx-deck-context?
- pptx-deck-context installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.