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
• SKILL.md does not explicitly describe the expected input format, output format, or step-by-step workflow for agents using this skill.
• No listed limitations or safe operating boundaries; for example, it does not clarify when the template is not suitable or how to handle very long/complex articles.
• The skill directory contains only SKILL.md and example.md; a dedicated usage or setup section in SKILL.md would improve clarity.
• Quality score needs 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
• SKILL.md does not explicitly describe the expected input format, output format, or step-by-step workflow for agents using this skill.
• No listed limitations or safe operating boundaries; for example, it does not clarify when the template is not suitable or how to handle very long/complex articles.
• The skill directory contains only SKILL.md and example.md; a dedicated usage or setup section in SKILL.md would improve clarity.
• Quality score needs 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
• SKILL.md does not explicitly describe the expected input format, output format, or step-by-step workflow for agents using this skill.
• No listed limitations or safe operating boundaries; for example, it does not clarify when the template is not suitable or how to handle very long/complex articles.
• The skill directory contains only SKILL.md and example.md; a dedicated usage or setup section in SKILL.md would improve clarity.
• Quality score needs 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
• SKILL.md does not explicitly describe the expected input format, output format, or step-by-step workflow for agents using this skill.
• No listed limitations or safe operating boundaries; for example, it does not clarify when the template is not suitable or how to handle very long/complex articles.
• The skill directory contains only SKILL.md and example.md; a dedicated usage or setup section in SKILL.md would improve clarity.
• Quality score needs review