pptx-deck-context
wshobson/agents
Establish narrative framework, sources, and design direction before authoring PPTX slides.
What is pptx-deck-context?
Prepares the foundational structure for a new editable PowerPoint deck by confirming audience, narrative framework, source lineage, and design constraints. Use this skill first when building a presentation to lock in business logic, source attribution, and visual direction before any slides are created.
- Confirm audience, decision scope, slide count, language, sources, and brand requirements
- Select and apply a narrative framework (McKinsey, SCQA, pyramid, MECE, action-title, assertion-evidence, exec-summary-first, or custom)
- Assign stable source IDs and plan source references for all metrics, quotations, charts, and factual claims
- Choose documented design direction from user brand guides, reference decks, or reusable design profiles
- Record framework, assumptions, source manifest, palette, typography, spacing, and signature elements in a summary document
How to install pptx-deck-context
npx skills add https://github.com/wshobson/agents --skill pptx-deck-contextHow to use pptx-deck-context
- 1.Confirm the target audience, key decision, intended slide count, language, and primary sources with the user
- 2.Offer a choice of narrative frameworks (McKinsey, SCQA, pyramid, MECE, action-title, assertion-evidence, exec-summary-first, or custom) and have the user select one
- 3.Create a source manifest with stable IDs for every metric, quotation, chart value, and factual claim
- 4.Review brand requirements, user brand guides, or reference decks to establish design direction
- 5.Document the framework, assumptions, source manifest, palette, typography, spacing, and signature elements in a summary before proceeding to slide authoring
Use cases
- Planning a client-facing strategy deck with multiple data sources and brand compliance requirements
- Establishing source attribution and narrative structure for a financial or executive presentation before slide authoring begins
- Locking in design direction and typography rules to ensure consistency across a multi-slide presentation
- Preparing a translated presentation by confirming language, cultural context, and localized design requirements
- Creating a reusable presentation template with documented design profiles and narrative frameworks
- Presentation strategists and designers planning multi-slide decks
- Business analysts and consultants preparing data-driven presentations
- Marketing and communications teams building branded decks
- Project managers coordinating presentation development with design and content teams
pptx-deck-context FAQ
Use this skill first, before authoring any slides or PPTX objects. It establishes the narrative structure, source lineage, and design constraints that guide all downstream slide creation.
Eight frameworks are offered: McKinsey, SCQA, pyramid, MECE, action-title, assertion-evidence, exec-summary-first, and custom. The user must explicitly choose one; the skill does not select silently.
Assign stable source IDs to every metric, quotation, chart value, and factual claim, then plan a source_ref for each. Keep long source material concise by requesting summaries or decision-relevant excerpts instead of including full documents.
Document the chosen framework, key assumptions, source manifest, color palette, typography rules, spacing guidelines, and signature design elements in the summary before authoring slides.
Only with recorded licensing evidence. Treat design references as design evidence, not content sources, and translate design signals into explicit fills, typography, spacing, and bounding boxes rather than relying on automatic layout engines.
Full instructions (SKILL.md)
Source of truth, from wshobson/agents.
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
- 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.
Related skills
More from wshobson/agents and the wider catalog.
pptx-quality-gates
Validate and repair PPTX decks for geometry, accessibility, editability, and package integrity.
pptx-reference-deck-analysis
Analyze reference PowerPoint decks for structure, theme, and layout without copying or modifying them.
pptx-slide-specification
Author coordinate-explicit JSON specifications for editable PPTX decks with precise layout control.
pptx-visual-assets
Select and place approved icons, images, SVGs, and diagrams in PowerPoint decks while preserving editability.
preference-optimization
Align fine-tuned models with preference data using DPO, ORPO, KTO, or SimPO.
projection-patterns
Build read models and projections from event streams for CQRS and event-sourced systems.