Guizang HTML to PPTX
PassAudited by ClawScan on May 3, 2026.
Overview
This is a coherent HTML-to-PPTX conversion skill that may read and write local project files and use local conversion tools, but the behavior is disclosed and aligned with its purpose.
This skill appears safe for its stated purpose. Use it from the correct project folder, review any generated or modified exporter script, and approve any dependency installation separately if the required local tools are not already present.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may read local files in the project directory to find and parse the deck.
The skill directs the agent to inspect local project files to locate an HTML deck. This is expected for the conversion task, but it is still local file access that users should understand.
Use the current working directory as the project root. Look first for `ppt/index.html`, then for `index.html`. If neither exists, search for a likely guizang HTML deck and proceed with the best match
Run it from the intended project directory and confirm the selected input deck if more than one deck may be present.
A local script may be added or changed in the project as part of the export workflow.
The skill can lead the agent to create or modify a local exporter script. That is purpose-aligned for producing a PPTX, but users should review generated or modified scripts before relying on them.
If there is already an `export_editable_pptx.py` or similar export script, inspect and improve it instead of starting over.
Review generated or modified exporter files before committing them or running them on sensitive projects.
If dependencies are missing, the user or agent may need to decide whether to install additional software.
The skill references external libraries and local tools, while the registry metadata declares no required binaries or install spec. The wording suggests using existing tools when available rather than automatically installing them.
Use `pptxgenjs` when the project already has Node dependencies for it. Use `python-pptx` when Python is the simpler available path. Use LibreOffice `soffice` plus `pdftoppm` for visual QA when available.
Use already-installed project dependencies where possible, and review any proposed package or tool installation before approving it.