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 include an explicit 'Limitations' or 'When Not to Use' section, so safe operating boundaries are only implied by the constraints.
• Financial research output is not financial advice; require human review before any live investment decision
• Some reference file excerpts appear truncated or incomplete, which could reduce usefulness if the actual files are not fully populated.
• No explicit guidance on how to handle unsafe or malicious user C++ code requests beyond general good-practice constraints.

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 include an explicit 'Limitations' or 'When Not to Use' section, so safe operating boundaries are only implied by the constraints.
• Financial research output is not financial advice; require human review before any live investment decision
• Some reference file excerpts appear truncated or incomplete, which could reduce usefulness if the actual files are not fully populated.
• No explicit guidance on how to handle unsafe or malicious user C++ code requests beyond general good-practice constraints.

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 include an explicit 'Limitations' or 'When Not to Use' section, so safe operating boundaries are only implied by the constraints.
• Financial research output is not financial advice; require human review before any live investment decision
• Some reference file excerpts appear truncated or incomplete, which could reduce usefulness if the actual files are not fully populated.
• No explicit guidance on how to handle unsafe or malicious user C++ code requests beyond general good-practice constraints.

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 include an explicit 'Limitations' or 'When Not to Use' section, so safe operating boundaries are only implied by the constraints.
• Financial research output is not financial advice; require human review before any live investment decision
• Some reference file excerpts appear truncated or incomplete, which could reduce usefulness if the actual files are not fully populated.
• No explicit guidance on how to handle unsafe or malicious user C++ code requests beyond general good-practice constraints.