ClawHub

Alpha — Technical Documentation

v1.0.0

Technical documentation specialist — READMEs, API references, setup guides, architecture decision records, changelogs. Structured, thorough, developer-audien...

⭐ 0· 81·0 current·0 all-time
by@renoblabs
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
Crypto
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (technical documentation) aligns with SKILL.md which lists README, API docs, setup guides, ADRs, changelogs and example inputs/outputs. Nothing in the skill asks for unrelated system access or credentials.
ℹ
Instruction Scope
SKILL.md stays within the documentation domain and gives clear inputs/outputs. One ambiguous claim: "Code examples are ... tested." The file does not explain how testing is performed (no commands, no test harness, no access to project files), so this is a quality claim rather than a clear runtime instruction.
✓
Install Mechanism
No install spec and no code files — lowest-risk, instruction-only skill. The SKILL.md references an external CLI command to "hire" the agent, but no install or download is required by the skill itself.
ℹ
Credentials
The skill declares no required environment variables or credentials. It does mention a price in ETH and a hiring CLI, which implies an external payment/workflow outside the skill; however, the skill does not request wallet keys or other secrets itself.
✓
Persistence & Privilege
always is false and the skill has no install or system persistence. It does not request modifications to other skills or system-wide configuration.
Assessment
This is an instruction-only documentation helper and appears internally consistent. Before installing or using: (1) be cautious if the agent asks you to run external commands (e.g., the referenced "mltl hire" CLI) or to provide wallet/private keys for ETH payments — the skill itself does not need those and you should not share secrets. (2) Ask the maintainer how "tested" code examples are produced if you need runnable tests or if the agent will be expected to execute code against your repositories. (3) Monitor any subsequent requests from the agent for file system access, network calls, or credentials; those would be outside the scope described here.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ee8z882sy6vm410e48x99mh84frz0

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments