code-mate-gemini 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 handling of gemini CLI version compatibility or availability of JSON output across versions.
• High-risk permission hints: Shell or command execution
• The skill relies on the prompt being safely constructed by the user, but does not warn about prompt injection risks from untrusted input.
• Production credentials, payments, or irreversible account changes without explicit human review