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 references three asset templates (war-room-grid.html, radar-map.html, analyst-dossier.html) but the submitted excerpt does not include these files. If they are missing from the repository, the skill's design guidance cannot be fully applied.
• Financial research output is not financial advice; require human review before any live investment decision
• The skill does not explicitly define how to handle user input that is not in the expected format (e.g., unstructured notes). It assumes the user provides competitive data, but does not specify a fallback or parsing strategy.
• Financial research output is not financial advice; require human review before any live investment decision.

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 references three asset templates (war-room-grid.html, radar-map.html, analyst-dossier.html) but the submitted excerpt does not include these files. If they are missing from the repository, the skill's design guidance cannot be fully applied.
• Financial research output is not financial advice; require human review before any live investment decision
• The skill does not explicitly define how to handle user input that is not in the expected format (e.g., unstructured notes). It assumes the user provides competitive data, but does not specify a fallback or parsing strategy.
• Financial research output is not financial advice; require human review before any live investment decision.

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 references three asset templates (war-room-grid.html, radar-map.html, analyst-dossier.html) but the submitted excerpt does not include these files. If they are missing from the repository, the skill's design guidance cannot be fully applied.
• Financial research output is not financial advice; require human review before any live investment decision
• The skill does not explicitly define how to handle user input that is not in the expected format (e.g., unstructured notes). It assumes the user provides competitive data, but does not specify a fallback or parsing strategy.
• Financial research output is not financial advice; require human review before any live investment decision.

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 references three asset templates (war-room-grid.html, radar-map.html, analyst-dossier.html) but the submitted excerpt does not include these files. If they are missing from the repository, the skill's design guidance cannot be fully applied.
• Financial research output is not financial advice; require human review before any live investment decision
• The skill does not explicitly define how to handle user input that is not in the expected format (e.g., unstructured notes). It assumes the user provides competitive data, but does not specify a fallback or parsing strategy.
• Financial research output is not financial advice; require human review before any live investment decision.