Index of every page on this site: llms.txt
All skills
wshobson avatar

/pptx-deck-context

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

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

Use this Skill: https://skilld.dev/gh/wshobson/agents/pptx-deck-context

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈28 tokens for metadata: the name and description. ≈380 when used: this file. ≈284 more on demand in 1 file.

Description uses 1.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈111 characters, or 1.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    The skill provides structured instructions for planning presentation decks, focusing on narrative frameworks, source tracking, and design consistency. No security risks or malicious patterns were detected.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: LOW · No issues

Signed by skilld at 4220308. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 4 months ago

README badge

README badge for wshobson/agents/pptx-deck-context