Tech Doc Writer
v1.3.4This skill should be used when the user wants to write detailed technical learning documentation, study notes, or knowledge summaries for deep learning, mach...
⭐ 2· 169·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (technical documentation authoring) aligns with the instructions and included reference examples. The skill does not request unrelated credentials, binaries, or installs.
Instruction Scope
The SKILL.md instructs the agent to fetch user-provided URLs and authoritative external docs, produce multi-part output automatically, and run a small local validation command (grep) against the generated document. These actions are consistent with creating high-quality docs, but they require network access to external webpages and the ability to read/write the generated file and run simple shell commands.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer and no third-party packages are pulled in.
Credentials
The skill requests no environment variables or credentials. It does recommend documenting environment variables when the doc topic is a tool/framework — this may prompt the agent to consult official docs, but the skill does not require or request access to the user's environment or secrets.
Persistence & Privilege
always is false and the skill is user-invocable. The SKILL.md's strong guidance to 'auto-advance' between parts means an agent allowed to invoke skills autonomously could generate multiple sequential outputs without repeated user confirmation; this is a behavior choice, not an elevated platform privilege.
Assessment
This skill is coherent with its goal and doesn't request credentials or installs. Before using it, decide whether you're comfortable allowing the agent to: (1) fetch content from user-supplied URLs and public documentation (network access), (2) read/write the generated markdown file and run a simple local command (grep) to validate headings, and (3) auto-continue producing subsequent Parts without pausing for your approval. Avoid supplying sensitive internal URLs or secrets as reference links, and review citations and code snippets for correctness before using them in production.Like a lobster shell, security has layers — review code before you run it.
docvk97dkktp10az1b80c68q0cqa9n83qxq0latestvk970qr1sffzd7jdw17m1v8j82x840z2vtechvk97dkktp10az1b80c68q0cqa9n83qxq0writevk97dkktp10az1b80c68q0cqa9n83qxq0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.