ppt2fig Export

Export specific pages from PPT, PPTX, or ODP files to cropped PDF via ppt2fig. Use when the user wants to convert presentation slides into paper-ready PDF fi...

Security Scan

The skill's behavior (calling a ppt2fig CLI or falling back to python -m ppt2fig) matches its stated purpose, but it is marked always:true (force-included) and its metadata references downloading an exe from GitHub releases — these raise proportionality and persistence concerns that you should review before enabling.

Purpose & Capability

The name/description (export PPT/PPTX/ODP pages to cropped PDF) aligns with the provided instructions and the small helper script: it locates a ppt2fig CLI in expected locations or falls back to python -m ppt2fig. No unrelated credentials, binaries, or system paths are requested.

Instruction Scope

SKILL.md clearly instructs the agent to run ppt2fig/ppt2fig-cli or the provided Python wrapper with user-supplied file paths and page ranges. The instructions do not attempt to read arbitrary files, access unrelated environment variables, or send data to external endpoints beyond running the CLI.

Install Mechanism

Top-level registry says 'instruction-only', but the skill metadata includes an install entry that downloads ppt2fig-cli.exe from a GitHub releases URL into ~/.openclaw/tools/ppt2fig-export. A GitHub Releases URL is a reasonable source, but auto-downloading and executing a binary deserves review (check publisher, release checksum/signature). The included Python helper is small and only invokes discovered binaries.

Credentials

The skill requests no environment variables or credentials. The helper script inspects local paths (home, cwd, repo dist) and uses shutil.which to find binaries — behavior consistent with its purpose and not requesting sensitive config or secrets.

Persistence & Privilege

The skill is flagged always:true, meaning it would be force-included in every agent run. There is no clear justification for permanent inclusion for a platform-specific (win32) tool-runner. Combined with the metadata for auto-downloading an executable and the ability to run local binaries, this increases the blast radius if the binary or skill were abused.

What to consider before installing

This skill appears to do what it claims (run ppt2fig to export slides), but review two things before enabling: 1) always:true — avoid forcing the skill into every agent run unless you explicitly need it permanently; prefer enabling it on demand. 2) The metadata may cause OpenClaw to download a Windows executable from the project's GitHub releases into ~/.openclaw/tools — verify the release, author, and (if available) checksums/signatures before allowing automatic download and execution. You can also inspect or run the included scripts locally (scripts/run_ppt2fig.py is brief and only invokes found binaries). If you don't want automatic downloads or permanent inclusion, decline installation or ask the publisher to remove always:true and provide an opt-in install flow.

Use ppt2fig to export slide pages to PDF.

Workflow:

1. Confirm the source presentation path exists.
2. Decide the page selection string. Examples: 1, 2, 1,3,5-7
3. Decide the backend. Defaults:
   • auto for normal use
   • libreoffice when cross-platform consistency matters
   • wps or powerpoint only when the user explicitly wants those backends
4. Decide whether to crop.
   • Use default cropping for paper figures.
   • Use --no-crop only when the user explicitly wants original margins.
5. Run the command.
6. Return the output PDF path and any backend-specific notes.

Preferred commands:

ppt2fig "/abs/path/input.pptx" --pages 2 -o "/abs/path/output.pdf"
ppt2fig "/abs/path/input.pptx" --pages 1,3,5-7 --backend libreoffice
ppt2fig "/abs/path/input.pptx" --pages 2 --backend wps
ppt2fig "/abs/path/input.pptx" --pages 2 --backend powerpoint --powerpoint-intent print

If ppt2fig is not on PATH, try:

ppt2fig-cli "/abs/path/input.pptx" --pages 2 -o "/abs/path/output.pdf"

If the binary is installed by OpenClaw or ClawHub, the helper script will first look in ~/.openclaw/tools/ppt2fig-export/ for the downloaded GitHub Release executable. If that is not present, it falls back to PATH, then to python -m ppt2fig:

python "{baseDir}/scripts/run_ppt2fig.py" "/abs/path/input.pptx" --pages 2 -o "/abs/path/output.pdf"

Behavior notes:

• auto backend priority is LibreOffice > WPS > PowerPoint.
• --list-backends prints what the current machine can use.
• Page numbers are 1-based.
• Output defaults to <input>.pages_<page-spec>.pdf when -o is omitted.
• PowerPoint image quality is limited by Microsoft's export API; --powerpoint-intent print is the highest-quality option exposed by the CLI.

Useful checks:

ppt2fig --list-backends
ppt2fig "/abs/path/input.pptx" --pages 999

Use the second command only when you need to validate page count or explain an out-of-range error.