Skip to the usage guide
pptx-slide-specificationby Seth Hobson

PPTX Slide Specification Skill.

A Claude Code and Codex skill for PPT and slide decks: authors coordinate-explicit JSON specifications for editable PPTX decks.

  • Presentations
  • PPTX
wshobson/agents · plugins/pptx-deck-creation/skills/pptx-slide-specification/SKILL.mdSKILL.md
--- name: pptx-slide-specification description: Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck. --- ## Required contract ## Authoring rules ## Build contract
Front matter and section headings read from the upstream file on 2026-09-14 · 1,954 characters in full

01 What it does

What the pptx-slide-specification Skill Does in Claude Code and Codex

Summary, workflow and outputs, all read from the skill's SKILL.md.

From the SKILL.mdRead 2026-09-14 · not a recorded run

In the Skill's Own Terms

This skill authors coordinate-explicit JSON specifications for editable PowerPoint decks where every element has final inch-based bounding boxes, stable IDs, styles, z-indexes, and classifications. No renderer may decide placement or shrink text after specification. The root JSON contains summary and slides; each slide has a stable ID, message-led title, accessibility reading order, and complete layout_tree.

Production summaries include an explicit layout_policy covering safe margin, content bottom, footer top, and minimum gap. Native objects (text, shape, line, table, image) replace any supporting visuals. Content text must be 9pt or greater. The builder starts from blank layouts, maps all bboxes with Inches(), and explicitly sets wrapping, auto-size, insets, anchors, alignment, fonts, colors, and line settings.

What it produces

  • JSON specification with summary and slides containing coordinate-explicit layout trees
See the example prompt ↗

How It Works

  1. 01
    Author Final Coordinates in Layout_tree

    Write absolute inch-based bounding boxes directly into the layout tree. No renderer may decide placement, shrink text, or infer layout after the audit.

  2. 02
    Declare Complete Structure per Slide

    Each slide must have a stable ID, message-led title, accessibility reading order, and a complete layout_tree that declares slide size, root group, and all objects.

  3. 03
    Specify All Object Properties Explicitly

    Every meaningful object must declare id, kind, role, classification, content, style, bbox, and z_index with final inch bboxes and styles.

  4. 04
    Builder Maps to Blank Slide Layout

    A task-local builder starts from a blank slide layout and maps all bboxes with Inches().

02 Find your fit

When to Use the pptx-slide-specification Skill

Use the pptx-slide-specification skill in Claude Code or Codex when the job is PPT and slide decks of this kind. Fit and limits below are taken from the skill's own file.

Good Fit

  • Authoring a coordinate-explicit JSON specification for an editable PPTX deck

    03 Inside the skill

    Rules the pptx-slide-specification Skill Gives Claude Code and Codex

    7 concrete instructions, defaults and limits the SKILL.md sets for the agent — the part of the file that changes the result.

    1. Use Stable Readable IDs and Positive Dimensions

      All IDs must be stable and readable. Use absolute groups and positive inch dimensions throughout the specification.

    2. Keep Content Inside Safe Margin and Above Footer

      Normal content must stay inside the safe margin and above the footer rail. Only background layout_design objects may be full bleed.

    3. Minimum Content Text Size Is 9pt

      Keep content text at 9 pt or greater. Shorten, resize, or split dense content before reducing type size.

    4. Use Native Objects for All Content

      Use native text, shape, line, table, and image objects. Recreate labels and values from any supporting visual as native objects instead of leaving them in images.

    5. Provide Accessibility and Source Metadata

      Give meaningful images alt text. Record source_ref for sourced claims. Production summary must contain accessibility metadata.

    6. Include Explicit Layout_policy in Summary

      Production summary must contain an explicit layout_policy that specifies safe margin, content bottom, footer top, and minimum gap.

    7. Builder Rejects Invalid Geometry

      The builder must reject zero or negative geometry before adding an object to ensure all shapes have valid dimensions.

    04 Put it to work

    Install pptx-slide-specification in Claude Code or Codex

    One npx skills add command, then a first task in your agent and a checklist for the result.

    Add pptx-slide-specification to Claude Code, Codex or Your Agent

    Run in your project; the installer asks which agent to add it to.

    Terminal
    npx skills add https://github.com/wshobson/agents --skill pptx-slide-specification

    Generic skills CLI form for plugins/pptx-deck-creation/skills/pptx-slide-specification/SKILL.md; the repository may document its own path.

    Give the Skill a First PPT and Slide Decks Task

    Written in the skill's own terms; replace the bracketed parts with your material.

    Starter prompt
    Create a PPTX specification for a [quarterly performance review] deck with [5 slides]. Include a title slide, three data slides showing [revenue trends, customer acquisition, and operational metrics], and a closing slide with next steps. Use a [corporate] layout with consistent spacing and ensure all chart labels are native text objects at minimum 9pt.

    Source: written from the SKILL.md in the skill's own terms.

    Check the First Result

    Before accepting the output, look for these in the transcript and the files:

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

    In OpenDesign import pptx-slide-specification from its SKILL.md link: Plugins → Add → Skill → Import from link, then pick it in the top bar.

    05 Open source, traceable

    Source, License and Verification

    Where this page's facts come from, and when they were last checked.

    Repository
    github.com/wshobson/agents Branch main
    Skill file
    plugins/pptx-deck-creation/skills/pptx-slide-specification/SKILL.md Content checksum recorded at verification; commit 4236bb9
    License
    MIT From LICENSE.
    Repository stars
    39,635 GitHub snapshot taken 2026-09-14 for the whole wshobson/agents repository, which contains 18 skills in this catalog. Not a rating or usage count for pptx-slide-specification.
    Verified by OpenDesign
    2026-09-14 Source file, path, license text and star count were checked. Not bundled in OpenDesign main (checked 2026-08-28); a live run has not been recorded on this page.

    Inside the SKILL.md

    1. Required contractDefines root JSON structure, slide requirements, layout tree contents, and required object fields
    2. Authoring rulesSpecifies ID conventions, margin rules, native object usage, accessibility requirements, type size minimums, and consistency standards
    3. Build contractExplains how builder processes specification from blank layouts, explicit property settings, and geometry validation
    The Skill's Own Description
    “Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck.”

    Front-matter description from SKILL.md. The full file is about 1,954 characters. Read the full file on GitHub.

    PPTX Slide Specification

    Run pptx-slide-specification on a Real PPT and Slide Decks Task.

    Download OpenDesign, import pptx-slide-specification from its SKILL.md link, paste the prompt above, and read the plan before the result.

    Terminal
    npx skills add https://github.com/wshobson/agents --skill pptx-slide-specification

    OpenDesign Desktop

    One design system. Every output unmistakably your brand

    Inside the full Vibe Design Workspace, use the same brand rules across websites, slide decks, interactive prototypes, dashboards, images, and HTML video. Connect Codex, Claude Code, Cursor, and other coding agents already on your computer, then create locally for free.

    • Web, slides, prototypes, dashboards, images, and video
    • 140+ design systems, plus the full template and skill library
    • Connect local Codex and 21+ coding agents · Free to use
    Download free

    Available for macOS and Windows