Pandoc
v1.0.2Convert documents between formats using pandoc. Supports HTML, Markdown, DOCX, PDF, EPUB, LaTeX, ODT, RST, Org, MediaWiki, JIRA, CSV, Jupyter notebooks, and...
⭐ 1· 591·3 current·3 all-time
byOliver Herklotz@oliver-hrkltz
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name, description, SKILL.md, and script consistently implement a pandoc-based document converter. However, the registry metadata lists no required binaries while the SKILL.md and scripts clearly require pandoc (and optionally local PDF engines like xelatex, wkhtmltopdf, weasyprint, etc.). The skill should have declared pandoc (and optionally known PDF engines) as required binaries.
Instruction Scope
SKILL.md instructs the agent to use the included scripts/convert.sh and to run pandoc for conversions. The script only operates on user-supplied input/output paths, checks that files exist, validates available local PDF engines, and invokes pandoc. There are no instructions to read unrelated system files, environment variables, or send data to external endpoints.
Install Mechanism
No install spec is present (instruction-only plus a local helper script), so nothing is downloaded or written by an installer. The included bash script is local and executed by the agent; there are no remote download URLs or extract operations in the package.
Credentials
The skill requests no environment variables or credentials, and the script does not attempt to read secrets or external config. It only checks for binaries on PATH and works with files the user provides. This is proportionate to a document-conversion utility.
Persistence & Privilege
The skill does not request permanent/always-on presence (always:false) and does not modify other skills or system-wide agent settings. It runs local commands at invocation time only.
Assessment
This skill is internally consistent and appears benign, but check a few practical things before installing and allowing autonomous use: (1) The package metadata did not declare pandoc as a required binary—ensure pandoc is installed on the agent's host (and install any PDF engine you need) before use. (2) Review scripts/convert.sh (included) yourself — the agent will run pandoc commands exactly as written, so don't pass sensitive files you wouldn't want processed locally. (3) The source/homepage in metadata is 'unknown' / no homepage provided — if you need stronger assurance, prefer a skill that links to an official repo or vendor. (4) If you are uneasy about autonomous invocation, restrict the skill to user-invocable only; otherwise it will run when the agent decides conversion is appropriate.Like a lobster shell, security has layers — review code before you run it.
latestvk971ykd4ask5051fs7dx064dvd82zen3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.