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 frontmatter describes a specific customer-onboarding workshop, but the body is mostly a generic template guide; this scope mismatch can confuse an agent about when and how to invoke the skill.
• Audit risk risky exceeds max_risk=medium
• Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
• The workflow in SKILL.md does not include the clarifying-question and critic-pass steps that appear in the example_prompt metadata, so an agent reading only SKILL.md may skip the essential pre-generation questions and final quality check.

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 frontmatter describes a specific customer-onboarding workshop, but the body is mostly a generic template guide; this scope mismatch can confuse an agent about when and how to invoke the skill.
• Audit risk risky exceeds max_risk=medium
• Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
• The workflow in SKILL.md does not include the clarifying-question and critic-pass steps that appear in the example_prompt metadata, so an agent reading only SKILL.md may skip the essential pre-generation questions and final quality check.

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 frontmatter describes a specific customer-onboarding workshop, but the body is mostly a generic template guide; this scope mismatch can confuse an agent about when and how to invoke the skill.
• Audit risk risky exceeds max_risk=medium
• Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
• The workflow in SKILL.md does not include the clarifying-question and critic-pass steps that appear in the example_prompt metadata, so an agent reading only SKILL.md may skip the essential pre-generation questions and final quality check.

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 frontmatter describes a specific customer-onboarding workshop, but the body is mostly a generic template guide; this scope mismatch can confuse an agent about when and how to invoke the skill.
• Audit risk risky exceeds max_risk=medium
• Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
• The workflow in SKILL.md does not include the clarifying-question and critic-pass steps that appear in the example_prompt metadata, so an agent reading only SKILL.md may skip the essential pre-generation questions and final quality check.