pandoc-docx
Analysis
This appears to be a straightforward pandoc-based document conversion skill, with expected local file access and command-line tool use.
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
"$SCRIPT_DIR/doc-read.sh" "$FILE" markdown | sed "s/$PATTERN/$REPLACEMENT/g" > "$TMPFILE" ... "$SCRIPT_DIR/doc-write.sh" "$FILE" "$TMPFILE" markdown
The replace workflow interpolates user-provided text into a sed replacement and then writes the result back to the original file. This is purpose-aligned editing, but special characters or a wrong path could cause unintended document changes.
"dependencies": { "pandoc": ">=2.0" }, "optionalDependencies": { "libreoffice": ">=6.0", "poppler-utils": ">=0.8", "texlive": ">=2020" }The skill depends on external document-processing tools with broad version ranges. These dependencies are expected for the purpose, but installation/provenance is left to the user rather than enforced by a pinned install spec.
pandoc "$INPUT" -o "$OUTPUT" $EXTRACT_MEDIA $REFERENCE_DOC $WRAP_MODE
The skill runs the local pandoc binary with user-selected files and options. This command execution is central to the documented conversion purpose and is not hidden.
