agenthub 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
• No explicit sandboxing or security restrictions are described for the spawned subagents—they execute commands in worktrees, which could be risky if not scoped carefully.
• High-risk permission hints: Shell or command execution
• The SKILL.md references external scripts (e.g., `dag_analyzer.py`, `references/agent-templates.md`) that are not provided in this excerpt; their safety and correctness cannot be verified from this submission alone.
• No guidance is given on limiting resource usage (e.g., maximum number of agents) or handling malicious task inputs that could lead to unintended actions.