pptx-slide-specification

Author coordinate-explicit JSON layout specifications for editable PPTX decks.

39.3k|4.2k|Updated Jul 24, 2025
One-click install
npx skills add https://github.com/wshobson/agents --skill pptx-slide-specification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pptx-slide-specification
Source: https://github.com/wshobson/agents/tree/main/plugins/pptx-deck-creation/skills/pptx-slide-specification
Command: npx skills add https://github.com/wshobson/agents --skill pptx-slide-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Building editable PowerPoint decks programmatically often fails because renderers infer placement, shrink text, or guess layout, producing broken slides. This Skill defines a strict JSON contract where every object has explicit inch-based coordinates, so the final deck matches the authored specification exactly.

Core Features & Use Cases

  • Coordinate-Explicit Layout Trees: Define slide size, groups, objects, bounding boxes, styles, and z-indexes directly in JSON with no renderer-side inference.
  • Layout Policy Enforcement: Apply safe margins, content bottom limits, footer rails, and minimum gaps so content never collides or overflows.
  • Accessibility and Audit Contract: Require reading order, alt text for images, source references for claims, and a minimum 9 pt content font size.
  • Use Case: When generating a quarterly review deck, author each slide's title, charts, and tables as native text, shape, line, table, and image objects with final bboxes, then hand the spec to a builder that maps everything with Inches(...) and rejects invalid geometry.

Quick Start

Use the pptx-slide-specification skill to author a JSON layout specification for a three-slide editable PPTX deck with explicit coordinates and a layout policy.

Frequently Asked Questions about pptx-slide-specification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a PPTX deck with exact element positioning in JSON?

Author a layout_tree per slide containing slide size, id-keyed groups and objects, and final inch bboxes for every element. A builder then maps each bbox with Inches(...) onto a blank slide layout, so no renderer decides placement afterward.

What JSON structure does a PPTX slide specification require?

The root JSON contains summary and slides. Each slide needs a stable id, message-led title, accessibility reading order, and a layout_tree with slide_size, root group, groups, objects, styles, bboxes, and z-indexes. The summary holds a layout_policy and accessibility metadata.

Can background images bleed to the slide edge in a PPTX layout spec?

Only objects classified as layout_design may be full bleed. All normal content must stay inside the safe margin and above the footer rail defined in the layout_policy, with at least the minimum gap between elements.

Why does text overflow happen in generated PowerPoint slides?

Overflow happens when bboxes are too small for the content or auto-size is left enabled. The contract requires explicit wrapping, disabled auto-size, text insets, and a repair order: move or resize bboxes first, shorten copy second, and reduce type only as a last resort above 9 pt.

What are the limitations of coordinate-explicit PPTX specifications?

The author must compute all geometry upfront, including grids, gaps, and z-order, since nothing is inferred later. Dense content must be split across slides rather than shrunk, and every object needs complete id, kind, role, classification, content, style, bbox, and z_index fields.