Skills · Content & docs

Pptx Deck Context

Unverified29/40

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

Originally by wshobson · MIT

Claude CodePartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
CursorPartialPlain prose you can paste in — but no Cursor rules file
CodexPartialPlain prose you can paste in — but no AGENTS.md
Gemini CLIPartialPlain prose you can paste in
CopilotPartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add pptx-deck-context

This command does not work yet — the CLI is still being built. Until then, use Raw in the reader below to take the file.

Who is stuck, and on what

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

The whole source

No sign-in, no blur, nothing truncated
pptx-deck-context/SKILL.md27 lines1.6 KBRawView on GitHub
Frontmatter — 2 properties
namepptx-deck-context
descriptionUse when preparing the narrative, sources, and design context for a new editable PPTX deck.
1---
2name: pptx-deck-context
3description: "Use when preparing the narrative, sources, and design context for a new editable PPTX deck."
4---A5No allowed-tools declared — no way to tell what this skill may touch
5 
6# PPTX Deck Context
7 
8Prepare the deck before coordinates or PPTX objects are authored. This skill owns the business narrative, source lineage, and design lock.
9 
10## Decision sequence
11 
121. Confirm audience, decision, slide count, language, sources, and brand requirements.
132. 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.
143. Assign stable source IDs and plan a `source_ref` for every metric, quotation, chart value, and factual claim.
154. 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`.
165. Record the framework, assumptions, source manifest, palette, typography, spacing, and signature elements in `summary` before authoring slides.
17 
18## Rules
19 
20- One slide should communicate one message, with an action-style title where the framework calls for it.
21- Treat design references as design evidence, not content or asset sources.
22- Do not copy external fonts, images, icons, or logos without recorded licensing evidence.
23- Translate design signals into explicit fills, typography, spacing, and bboxes; do not rely on an automatic layout engine.
24- Keep long source material concise. Ask for a summary or decision-relevant excerpt instead of turning a deck spec into a document dump.
25 
26See `references/design-profiles.md` for reusable profile guidance.
27 

Reviews

Installed this one?Write the first review and take the Trailblazer badge.

Reviews only open after a real install, so this is empty — and we leave it empty rather than invent one.

Alternatives

Also in Content & docs