Pptx Slide Specification
Unverified●29/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add pptx-slide-specificationWho is stuck, and on what
Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck.
The whole source
Frontmatter — 2 properties
| name | pptx-slide-specification |
|---|---|
| description | Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck. |
| 1 | --- |
| 2 | name: pptx-slide-specification |
| 3 | description: "Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck." |
| 4 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 5 | |
| 6 | # PPTX Slide Specification |
| 7 | |
| 8 | Author final coordinates directly in `layout_tree`. No renderer may decide placement, shrink text, or infer layout after the audit. |
| 9 | |
| 10 | ## Required contract |
| 11 | |
| 12 | - The root JSON contains `summary` and `slides`. |
| 13 | - Every slide has a stable `id`, a message-led `title`, an accessibility reading order, and a complete `layout_tree`. |
| 14 | - A layout tree declares slide size, root group, id-keyed groups and objects, final inch bboxes, styles, z-indexes, and classifications. |
| 15 | - Every meaningful object has `id`, `kind`, `role`, `classification`, `content`, `style`, `bbox`, and `z_index`. |
| 16 | - Production `summary` contains an explicit `layout_policy` (safe margin, content bottom, footer top, minimum gap) and accessibility metadata. |
| 17 | |
| 18 | ## Authoring rules |
| 19 | |
| 20 | 1. Use stable readable IDs, absolute groups, and positive inch dimensions. |
| 21 | 2. Keep normal content inside the safe margin and above the footer rail. Only background `layout_design` objects may be full bleed. |
| 22 | 3. Use native `text`, `shape`, `line`, `table`, and `image` objects. Recreate labels and values from any supporting visual as native objects. |
| 23 | 4. Give meaningful images alt text. Record `source_ref` for sourced claims. |
| 24 | 5. Keep content text at 9 pt or greater; shorten, resize, or split dense content before reducing type. |
| 25 | 6. Use shared grids, consistent gaps, explicit color, explicit font size, and an intentional z-order. |
| 26 | |
| 27 | ## Build contract |
| 28 | |
| 29 | 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. |
| 30 | |
| 31 | See `references/layout-contract.md` for the compact schema and repair guidance. |
| 32 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Research Review via External Reviewer Backend (ultra reasoning)Get a deep critical review of research from an external reviewer backend (Codex or manual). Use when user says "review my research", "help me review", "get external review", or wants critical feedback on research ideas, papers, or experimental results.●····●38/40Training CheckPeriodically check WandB metrics during training to catch problems early (NaN, loss divergence, idle GPUs). Avoids wasting GPU hours on broken runs. Use when training is running and you want automated health checks.●····●37/40Changelog AutomationAutomate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.◐····●36/40Hermes Tweet> Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.◐····●36/40