# Pptx Deck Context

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

Source: https://skillsagentes.com/skills/wshobson/agents/pptx-deck-context
Repository: https://github.com/wshobson/agents
Author: wshobson
License: MIT
Updated: hace 27 días
Context cost: 23 tok installed, 415 tok once triggered, 699 tok with every bundled file
Bundle: 2 files, 3 KB
Permissions requested: none declared

## Install

```bash
npx -y skills add wshobson/agents --skill pptx-deck-context --agent claude-code
```

## What it does

- Define la narrativa de negocio, el linaje de fuentes y el bloqueo de diseño antes de crear un PPTX
- Asigna IDs de fuente estables y planifica un source_ref para cada métrica, cita o valor de gráfico
- Elige un framework narrativo (mckinsey, scqa, pyramid, mece, action-title, assertion-evidence, exec-summary-first o custom)
- Selecciona una dirección de diseño documentada a partir de guía de marca, deck de referencia o perfiles reusables
- Registra framework, supuestos, manifiesto de fuentes, paleta, tipografía, espaciado y elementos de firma en el summary

## Use it when

- Al preparar la narrativa, fuentes y contexto de diseño para un nuevo deck PPTX editable, antes de escribir coordenadas u objetos PPTX

## What triggers it

- "Prepárame el contexto y la narrativa para un nuevo deck PPTX"
- "Ayúdame a definir el framework y las fuentes antes de armar las diapositivas"
- "Necesito bloquear el diseño y las fuentes antes de crear el PPTX"

## Before you install

- Conviene tener disponible una guía de marca o un deck de referencia para basar la dirección de diseño.

## Files

- SKILL.md — 2 KB
- references/design-profiles.md — 1 KB

## SKILL.md

Reproduced verbatim from wshobson/agents under MIT. This section is the upstream document and is in English.

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

---

Skills Agentes — https://skillsagentes.com/skills/wshobson/agents/pptx-deck-context