Preparing the narrative, sources

Pptx deck context

by wshobson · MIT license · ★ 39,857 on GitHub · updated Sep 21

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

---
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

Overview

Prepare the deck before coordinates or PPTX objects are authored. This skill owns the business narrative, source lineage, and design lock.

Manual install (npx, ZIP)

Claude Codenpx skills add wshobson/agents --skill pptx-deck-context -g -a claude-code

Claude Code (degit)npx degit wshobson/agents/plugins/pptx-deck-creation/skills/pptx-deck-context#main ~/.claude/skills/pptx-deck-context

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md1.6 KB

Read SKILL.md here

wshobson/main1 file shown

SKILL.md1.6 KB

Browse every file on GitHub↗

SKILL.md

Show the full text27 lines

pptx-deck-context/SKILL.md27 lines · 1.6 KB

PreviewCode

Outline

RawView on GitHub

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, or custom; do not choose silently.
Assign stable source IDs and plan a source_ref for 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 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.

1	---
2	name: pptx-deck-context
3	description: "Use when preparing the narrative, sources, and design context for a new editable PPTX deck."
4	---
5
6	# PPTX Deck Context
7
8	Prepare 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
12	1. Confirm audience, decision, slide count, language, sources, and brand requirements.
13	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.
14	3. Assign stable source IDs and plan a `source_ref` for every metric, quotation, chart value, and factual claim.
15	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`.
16	5. 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
26	See `references/design-profiles.md` for reusable profile guidance.
27