html-ppt

HTML PPT

When to Use

Use when the user has a structured single-slide HTML file or small HTML slide family and wants an editable .pptx made of native PowerPoint objects.

Use only when the HTML matches an existing preset or when the user accepts adding a new preset first.

Do not promise arbitrary HTML/CSS fidelity. Do not use this as a screenshot exporter.

Current Presets

• v9-architecture: header, title, summary box, driver panel, architecture stack, judgement chain.
• ai-runtime-page: header, title, lead box, input/output chips, runtime modules, support layers, base layer.

First-Run Setup

Run the bundled environment check through the standard Skill Runner:

"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" html-ppt check_env -- --json

Do not run npm install or npm ci inside the installed Marketplace skill directory. If the check reports a missing runtime dependency, surface it as a packaging/runtime issue instead of modifying the protected install.

Read references/setup.md when using the skill on a new machine or dependency state is unclear.

Workflow

1. Inspect the HTML and identify the slide family.
2. Read references/preset-decision-rules.md if preset fit is uncertain.
3. Reuse an existing preset only when the page family is genuinely close.
4. If no preset fits, add a new preset instead of forcing a bad conversion:

• DOM extraction rules
• layout/render mapping rules
• QA/preflight rules

1. Convert with the bundled Node script.
2. Run preflight QA on the generated model.
3. Open or preview the PPTX when visual fidelity matters. Check spacing, overflow, arrow direction, text wrapping, and object editability.

Commands

"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" html-ppt check_env -- --json
"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" html-ppt html_to_pptx -- <input.html> <output.pptx> [--preset=v9-architecture|ai-runtime-page] [--dump-model <file.json>]
"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" html-ppt preflight_qa -- <model.json> [--preset=v9-architecture|ai-runtime-page] [--report <report.json>]

Return Format

For a successful conversion, return:

• generated .pptx path
• preset used
• whether dependencies and QA passed
• visual review status
• known fidelity limitations

For unsupported HTML, return:

• why no preset fits
• whether a new preset is recommended
• the minimum extraction/layout/QA work needed before conversion

External Dependencies

• Node.js 18+ recommended.
• npm.
• Bundled dependencies from package.json / package-lock.json.
• A PowerPoint-compatible viewer is recommended for final visual QA.

References

• references/setup.md: dependency setup and portability.
• references/preset-decision-rules.md: decide reuse vs new preset.
• references/presets.md: current preset details.
• references/preset-template.md: how to add a new preset.
• references/qa-heuristics.md: preflight and visual QA rules.
• references/usage-principles.md: usage principles.
• references/roadmap.md: future high-fidelity measurement ideas.

Limits and Known Issues

• This skill parses semantic blocks and maps them to PPTX objects. It does not render arbitrary browser layout.
• CSS effects, fonts, gradients, SVGs, responsive behavior, and canvas content may not translate.
• Fidelity depends on preset quality and QA iteration.
• Keep generated PPTX editable; do not silently fall back to one flattened screenshot.