OpenClaw Doc Generator
v1.1.0Generates documentation from code. Creates API docs, README updates, architecture diagrams, and keeps documentation in sync with code changes.
⭐ 0· 35·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the included code: CLI entrypoint, API extraction, and README updater. The files and commands shown are what you'd expect for a doc generator.
Instruction Scope
Runtime instructions run local Python scripts that read source files and write documentation and README.md. This is expected, but the skill will modify files in your repo (and the SKILL.md even suggests CI steps that run git push). There are no instructions to read unrelated system credentials or send data to external endpoints.
Install Mechanism
No install spec — instruction-only with bundled scripts. Nothing is downloaded or extracted from external URLs, so install risk is low. The code runs from the skill's scripts when invoked.
Credentials
The skill declares no required environment variables or credentials, which aligns with its purpose. The CI example in SKILL.md includes git push steps (which in practice require CI secrets) — those are just examples but could lead to unexpected pushes if copied verbatim in CI. Also the code conditionally attempts to add a 'c-support' path to sys.path (parent-parent-parent / 'c-support' / 'lib') to import a C parser if present; that may import code from an adjacent directory if it exists.
Persistence & Privilege
always:false (normal). The skill will write/update files in the repository (docs/, README.md). While it doesn't persist as an always-enabled skill or modify other skills, file-write behavior means it can change user content — review changes before committing or enabling automated CI commits.
Assessment
This skill appears to do what it says: generate docs and update README. Before using it: 1) Run it in a safe/test copy of your repo first because it writes/overwrites files (docs/, README.md). 2) If you plan to add the suggested CI steps, ensure the CI git push is intentional and that your CI tokens have appropriate scope. 3) Note SKILL.md references a diagram_generator file that isn't present in the bundle and api_generator conditionally imports a 'c-support' module from a nearby path — verify whether that external code exists and is trusted. 4) Review the generated changes (don't auto-commit without inspection). If you want, I can point out the exact lines where files are written and where external imports occur.Like a lobster shell, security has layers — review code before you run it.
latestvk97avye0bq1bczqs0fdh7k71jn842qq0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.