pptx-slide-specification
Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck.
Profile →npx skills add wshobson/agents --skill pptx-slide-specification --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Required contract
- Authoring rules
- Build contract
What does the pptx-slide-specification skill do?
Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck.
How do I install it?
Run `npx skills add wshobson/agents --skill pptx-slide-specification --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From wshobson/agents, a repository with 38,479 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.