Claude Cursor Skill

pptx-deck-context

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

LLM Mart · 0 points · 14 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download wshobson-agents-plugins_pptx-deck-creation_skills_pptx-deck-context-554237f.zip · 1 KB

wshobson/agents 40003 4267 forks MIT Updated 8h ago

Part of wshobson/agents — 170 skills

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/pptx-deck-creation/skills/pptx-deck-context

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart

Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

Files (agents)

references

design-profiles.md 1.1 KB

# Design Profile Guidance

Use a profile as design evidence, then lock its palette, typography, spacing, and signature element in `summary.design_context` before coordinate authoring.

| Profile | Best for | Signals |
| --- | --- | --- |
| `fluent-ui-design-tokens` | enterprise and Microsoft-aligned decks | restrained neutrals, clear hierarchy, token-based spacing, modest radii |
| `primer-primitives` | GitHub and developer-focused decks | crisp surfaces, strong text contrast, functional accents, compact labels |
| `editorial-minimal` | executive narrative and research decks | generous whitespace, high-contrast type, limited palette, one visual motif |

## Rules

- Prefer an explicit user brand guide. Otherwise use read-only reference-deck evidence, then a documented profile.
- Record profile ID, source URL when applicable, license information when known, and the resulting style lock.
- Use public design signals for inspiration only. Do not copy proprietary images, logos, fonts, screenshots, or slide content.
- Translate the lock into explicit `layout_tree` colors, fills, typography, rules, card shells, and bboxes.

SKILL.md 1.6 KB

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