pptx-deck-context — Claude Code skill: what it does, how to install
Locks down deck narrative, source citations, and visual styling before any slides or PPTX objects are authored.
/plugin marketplace add wshobson/agents
/plugin install pptx-deck-creation@claude-code-workflowsWhat pptx-deck-context does
The skill establishes the deck story, tracks source lineage, and locks design rules before slide generation starts. It confirms audience expectations and brand constraints up front. Framework choice is never silent. The assistant offers options like mckinsey, scqa, pyramid, mece, action-title, assertion-evidence, or exec-summary-first.
Every claim, quote, or chart value receives a stable source identifier in summary. Visual decisions draw from a brand guide, reference deck evidence, or profiles in references/design-profiles.md. Layout never relies on automatic positioning engines. Fills, spacing, and bounding boxes must be declared explicitly.
Use this skill when presenting analysis that demands verified sources. If you only need a fast throwaway outline, the upfront verification creates unnecessary friction.
What it helps with
- Lock the presentation narrative before authoring slide objects
- Map metrics and quotations to persistent source identifiers
- Establish explicit typography and fills without layout engines
- Summarize dense source documents into decision-relevant excerpts
Example prompts for the agent
- Prepare the presentation context using the scqa framework
- Lock sources and design specifications before generating PPTX slides
How to install pptx-deck-context
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install pptx-deck-creation@claude-code-workflowsThis installs the whole pptx-deck-creation plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill pptx-deck-context -a claude-code3Manually: put the files in place
~/.claude/skills/pptx-deck-context/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pptx-deck-context/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill pptx-deck-context -a codex2Manually: put the files in place
.agents/skills/pptx-deck-context/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill pptx-deck-context -a cursor2Manually: put the files in place
.cursor/skills/pptx-deck-context/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents pptx-deck-context2Manually: put the files in place
.github/skills/pptx-deck-context/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/pptx-deck-creation/skills/pptx-deck-contextManually: put the files in place
.devin/skills/pptx-deck-context/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about pptx-deck-context
How to install pptx-deck-context in Claude Code?
Run npx skills add wshobson/agents --skill pptx-deck-context -a claude-code in your terminal.
What does pptx-deck-context do?
It formalizes the presentation narrative, links claims to sources, and sets design specifications before slide shapes are built.
Where does pptx-deck-context get styling rules?
It uses your brand guide, extracts styles from reference decks, or applies prebuilt options from references/design-profiles.md.
Source text
SKILL.md · MIT
--- 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.
© kimtth · MIT · wshobson/agents