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 invokes local code execution (uv sync and dev/loadtest/run.py), so it should be used only in a trusted repository checkout; no explicit warning against running it on untrusted code.
• No OpenAgentSkill engagement data yet
• High-risk permission hints: Shell or command execution
• The generated summary.md is read and relayed by the agent; if the load test output were ever tampered with, it could inject instructions into the agent context, though this is a low-risk local-file scenario.

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 invokes local code execution (uv sync and dev/loadtest/run.py), so it should be used only in a trusted repository checkout; no explicit warning against running it on untrusted code.
• No OpenAgentSkill engagement data yet
• High-risk permission hints: Shell or command execution
• The generated summary.md is read and relayed by the agent; if the load test output were ever tampered with, it could inject instructions into the agent context, though this is a low-risk local-file scenario.

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 invokes local code execution (uv sync and dev/loadtest/run.py), so it should be used only in a trusted repository checkout; no explicit warning against running it on untrusted code.
• No OpenAgentSkill engagement data yet
• High-risk permission hints: Shell or command execution
• The generated summary.md is read and relayed by the agent; if the load test output were ever tampered with, it could inject instructions into the agent context, though this is a low-risk local-file scenario.

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 invokes local code execution (uv sync and dev/loadtest/run.py), so it should be used only in a trusted repository checkout; no explicit warning against running it on untrusted code.
• No OpenAgentSkill engagement data yet
• High-risk permission hints: Shell or command execution
• The generated summary.md is read and relayed by the agent; if the load test output were ever tampered with, it could inject instructions into the agent context, though this is a low-risk local-file scenario.