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.md does not instruct the agent to treat external tool output as untrusted data; malicious content returned from LinkedIn or other sources could attempt prompt injection.
• No OpenAgentSkill engagement data yet
• The API map is essentially a placeholder: every entry says 'See sandbase_describe_tool for details,' so the skill does not document what each tool actually does or returns.
• No explicit privacy or data-minimization guidance is provided for handling personal information of leads, despite the skill being centered on collecting prospect intelligence.

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.md does not instruct the agent to treat external tool output as untrusted data; malicious content returned from LinkedIn or other sources could attempt prompt injection.
• No OpenAgentSkill engagement data yet
• The API map is essentially a placeholder: every entry says 'See sandbase_describe_tool for details,' so the skill does not document what each tool actually does or returns.
• No explicit privacy or data-minimization guidance is provided for handling personal information of leads, despite the skill being centered on collecting prospect intelligence.

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.md does not instruct the agent to treat external tool output as untrusted data; malicious content returned from LinkedIn or other sources could attempt prompt injection.
• No OpenAgentSkill engagement data yet
• The API map is essentially a placeholder: every entry says 'See sandbase_describe_tool for details,' so the skill does not document what each tool actually does or returns.
• No explicit privacy or data-minimization guidance is provided for handling personal information of leads, despite the skill being centered on collecting prospect intelligence.

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.md does not instruct the agent to treat external tool output as untrusted data; malicious content returned from LinkedIn or other sources could attempt prompt injection.
• No OpenAgentSkill engagement data yet
• The API map is essentially a placeholder: every entry says 'See sandbase_describe_tool for details,' so the skill does not document what each tool actually does or returns.
• No explicit privacy or data-minimization guidance is provided for handling personal information of leads, despite the skill being centered on collecting prospect intelligence.