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

/pptx-slide-specification

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

Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck.

Use this Skill: https://skilld.dev/gh/wshobson/agents/pptx-slide-specification

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈31 tokens for metadata: the name and description. ≈450 when used: this file. ≈371 more on demand in 1 file.

Description uses 1.6% 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 ≈126 characters, or 1.6%.

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

Author final coordinates directly in layout_tree. No renderer may decide placement, shrink text, or infer layout after the audit.

Required contract

  • The root JSON contains summary and slides.
  • Every slide has a stable id, a message-led title, an accessibility reading order, and a complete layout_tree.
  • A layout tree declares slide size, root group, id-keyed groups and objects, final inch bboxes, styles, z-indexes, and classifications.
  • Every meaningful object has id, kind, role, classification, content, style, bbox, and z_index.
  • Production summary contains an explicit layout_policy (safe margin, content bottom, footer top, minimum gap) and accessibility metadata.

Authoring rules

  1. Use stable readable IDs, absolute groups, and positive inch dimensions.
  2. Keep normal content inside the safe margin and above the footer rail. Only background layout_design objects may be full bleed.
  3. Use native text, shape, line, table, and image objects. Recreate labels and values from any supporting visual as native objects.
  4. Give meaningful images alt text. Record source_ref for sourced claims.
  5. Keep content text at 9 pt or greater; shorten, resize, or split dense content before reducing type.
  6. Use shared grids, consistent gaps, explicit color, explicit font size, and an intentional z-order.

Build contract

A task-local builder starts from a blank slide layout and maps all bboxes with Inches(...). Explicitly set wrapping, disabled auto-size, text insets, anchors, alignment, fonts, colors, line settings, image aspect ratio, and hidden-slide state. Reject zero or negative geometry before adding an object.

See references/layout-contract.md for the compact schema and repair 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

    This skill provides a structured framework and guidelines for defining PowerPoint slide layouts in JSON format. It contains no executable code, network operations, or instructions that could lead to security compromises.

  • 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-slide-specification