cs-clean-code 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.md excerpt appears truncated at the end of the Boundaries section; the full file should be verified to ensure the section is complete.
• High-risk permission hints: Secrets or environment access
• Permission surface may require sandboxing
• The skill instructs agents to edit code and update docs but does not explicitly state restrictions around running destructive commands, modifying git history, or handling secrets.