Office live ppt

Skill binle11/live-office-ppt/integrations/openclaw/office-live-ppt

Render JSON slide specs into native editable PowerPoint decks through desktop PowerPoint COM automation.

Install

npx -y skills add binle11/live-office-ppt --skill office-live-ppt

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create, edit, and debug PowerPoint decks with the Live Office PPT workflow: write a JSON slide spec, optionally generate bitmap assets first, then run a PowerShell COM renderer that opens desktop PowerPoint and draws native editable shapes, text, connectors, and pictures live. Use for PPT/PPTX tasks that require visible Office drawing, PowerPoint COM automation, live deck review, or native editable PowerPoint objects.

SKILL.md

1.9 KB, 321 tokens by cl100k_base, as published. Nobody here has run it

Office Live PPT

Use this skill only on Windows machines with desktop Microsoft PowerPoint available. The renderer is a local Office automation workflow, not a headless server renderer.

Workflow

Locate the live-office-ppt repository.
Create the deck JSON spec in the user's project directory.
If bitmap visuals are needed, generate or source them first, save them under the deck project's assets/images/, and add them to top-level assets.

Validate before opening PowerPoint:

powershell -ExecutionPolicy Bypass -File <live-office-ppt>\render-live-ppt.ps1 `
  -Spec <deck-spec.json> `
  -ValidateOnly

Render with PowerPoint visible:

powershell -ExecutionPolicy Bypass -File <live-office-ppt>\render-live-ppt.ps1 `
  -Spec <deck-spec.json> `
  -StepDelayMs 80 `
  -Overwrite

Inspect the live result, revise JSON, and rerun.

Authoring Rules

Prefer native PowerPoint text, shapes, and connectors over rasterized slides.
Use editable PowerPoint text for labels and slide copy.
Keep coordinates deterministic. The default 16:9 canvas is 960 x 540.
Use fit: "cover" for full-bleed images and fit: "contain" for diagrams or screenshots that must not crop.
Keep project-specific materials outside reusable repository examples.

Gives 0 of the 12 instructions most automation workflows skills give in 321 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-06

write conventional commit messagesin 36 of 745, across 35 files
delete branches after mergein 30 of 745, across 21 files
make atomic commitsin 25 of 745, across 15 files
write minimal code to pass testsin 22 of 745, across 10 files
run tests before committingin 21 of 745, across 13 files
re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
use try-catch for error handlingin 20 of 745, across 6 files
write tests before implementationin 20 of 745, across 8 files
configure branch protection rulesin 19 of 745, across 5 files
explain the why in commit messagesin 19 of 745, across 9 files
refactor code while tests remain greenin 19 of 745, across 6 files
Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

Generate bitmap assets before rendering
Validate before opening PowerPoint
Render with PowerPoint visible
Use editable text for labels
Prefer native shapes over rasters
Keep coordinates deterministic

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.