Technical Documentation Engine
v1.1.0Complete technical documentation system — from planning through maintenance. Covers READMEs, API docs, guides, architecture docs, runbooks, and developer por...
⭐ 0· 881·2 current·2 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (technical documentation engine) match the SKILL.md and README contents: audit checklists, templates, scoring, and maintenance guidance. There are no unrelated environment variables, binaries, or install steps requested that would be disproportionate to producing docs.
Instruction Scope
The runtime instructions focus on auditing and producing documentation and templates. They assume access to the project/codebase for an audit (expected for this purpose) but do not instruct the agent to read unrelated system files, secrets, or external endpoints for data exfiltration. Templates include placeholder examples (e.g., an API_KEY export) which are examples for docs, not required credentials for the skill itself.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk or downloaded during install. That is the lowest-risk model and is proportionate for a templates-and-guidance skill.
Credentials
The skill declares no required environment variables, credentials, or config paths. The README/templates show example env snippets (API_KEY) for users to include in their projects, but the skill itself doesn't request or require secrets.
Persistence & Privilege
always:false (normal). The skill can be invoked autonomously by the agent (platform default). This is expected for skills, and there is no indication the skill requests permanent system-level presence or modifies other skills/configuration.
Assessment
This is an instruction-only documentation template and audit skill — low-risk compared with code-based skills. Before installing: (1) Understand it will ask the agent to inspect your repository to produce audits and docs (only grant repository access if you trust the agent). (2) The templates include example env variables (API_KEY) for docs; do not paste real secrets into prompts or skill configuration. (3) The README links to external paid 'context packs' and webpages — those are marketing/optional. If you need stronger guarantees, review any outputs locally before committing generated docs to repositories or pipelines.Like a lobster shell, security has layers — review code before you run it.
adrvk97eax4qe6btfahy2c3vwa4qy5816pgqapi-docsvk97c49f84j6eafk6sxjfc9t9sd819e1echangelogvk97eax4qe6btfahy2c3vwa4qy5816pgqdevdocsvk97c49f84j6eafk6sxjfc9t9sd819e1edocumentationvk97c49f84j6eafk6sxjfc9t9sd819e1elatestvk97c49f84j6eafk6sxjfc9t9sd819e1ereadmevk97c49f84j6eafk6sxjfc9t9sd819e1erunbookvk97eax4qe6btfahy2c3vwa4qy5816pgqrunbooksvk97c49f84j6eafk6sxjfc9t9sd819e1etechnical-writingvk97c49f84j6eafk6sxjfc9t9sd819e1etemplatesvk97c49f84j6eafk6sxjfc9t9sd819e1e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.