download-docs Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• The skill depends on external scripts (github.sh, url.sh) from the build-docs skill, which are not included in this submission. This creates a hidden dependency that may cause failures if the build-docs skill is not present.
• High-risk permission hints: Shell or command execution
• Permission surface may require sandboxing
• The skill uses bash -c with user-supplied config names and versions. While the expected format is constrained, there is no explicit validation to prevent path traversal or command injection if a malicious config name is provided.