/pptx-slide-specification
Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck.
One skill from wshobson-agents.
shell
$ npx -y skills add wshobson/agents --skill pptx-slide-specification --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/pptx-slide-specification
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck.
Stats
Stars38,169
Forks4,092
LanguagePython
LicenseMIT
Ships with wshobson-agents
SKILL.md
pptx-slide-specification.SKILL.md
--- name: pptx-slide-specification description: "Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck." --- # 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.
