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 relies on external tools (uv, Python) and may download a ~1GB model for the 'exp' diagnostic mode, which requires user consent and could be a minor security consideration.
• The skill is highly detailed and complex, which might be overwhelming for some users, but the quick/full mode distinction helps manage complexity.
• Quality score needs review
• Production credentials, payments, or irreversible account changes without explicit human review

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 relies on external tools (uv, Python) and may download a ~1GB model for the 'exp' diagnostic mode, which requires user consent and could be a minor security consideration.
• The skill is highly detailed and complex, which might be overwhelming for some users, but the quick/full mode distinction helps manage complexity.
• Quality score needs review
• Production credentials, payments, or irreversible account changes without explicit human review

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 relies on external tools (uv, Python) and may download a ~1GB model for the 'exp' diagnostic mode, which requires user consent and could be a minor security consideration.
• The skill is highly detailed and complex, which might be overwhelming for some users, but the quick/full mode distinction helps manage complexity.
• Quality score needs review
• Production credentials, payments, or irreversible account changes without explicit human review

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 relies on external tools (uv, Python) and may download a ~1GB model for the 'exp' diagnostic mode, which requires user consent and could be a minor security consideration.
• The skill is highly detailed and complex, which might be overwhelming for some users, but the quick/full mode distinction helps manage complexity.
• Quality score needs review
• Production credentials, payments, or irreversible account changes without explicit human review