Tech Docx Writer

PassAudited by ClawScan on May 17, 2026.

Overview

This skill is coherent for generating Word documents, but it may inspect project materials and run a local Python conversion script.

This skill appears safe for its stated purpose. Before using it, limit it to the intended repository, wiki pages, template, and output path; review the approved Markdown draft and final .docx; and ensure any required Python packages come from trusted sources.

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.

What this means

Private code, wiki details, or repository history could be incorporated into the generated document if the source scope is too broad.

Why it was flagged

The skill directs the agent to read potentially proprietary project sources and use them as context for generated documentation.

Skill content
Gather factual context from project wikis, codebases, or reference docs. ... Read the codebase files or use `git log` / `grep` / `Read`
Recommendation

Provide specific source paths and templates, avoid including secrets, and review the Markdown draft and final document before sharing.

What this means

The agent will run a locally generated script that reads the template and writes a Word document, so path choices and script behavior matter.

Why it was flagged

The skill explicitly requires generated local Python execution. This is central to the document-generation purpose and is disclosed, but it is still a behavior users should notice.

Skill content
You MUST write and execute a python script (using `python-docx` and `lxml`) to inject the Markdown into the target `.docx` template.
Recommendation

Run it only in the intended project/work directory, use trusted templates, and ask to inspect the generated script if the document contains sensitive material.

What this means

If the required Python libraries are missing, the user or agent may need to install them separately, which should be done from trusted sources.

Why it was flagged

The workflow depends on python-docx and lxml, but dependency setup and provenance are not declared in install metadata.

Skill content
No install spec — this is an instruction-only skill.
Recommendation

Use a known Python environment and trusted, preferably pinned, package versions for python-docx and lxml.