clean-gone 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
• Low GitHub adoption signal
• The skill does not explicitly handle repositories with multiple remotes; `git fetch --prune` prunes only the default remote, so branches tracking other remotes may be evaluated against stale state.
• High-risk permission hints: Shell or command execution
• The `Read` allowed-tool is broad. If the runtime supports path-scoped permissions, it would be safer to restrict reads to the relevant workflow/config files.