Pre-install eval
exit-strategies Eval report.
A machine-readable install decision for agents: task fit, Trust Score, Audit Score, install safety, permission surface, and a concrete validation plan before this skill touches a workspace.
manual review
Test manually in an isolated workspace and compare against safer alternatives.
Required gates
Checks an agent must pass before install
Task fit
84
Task wording matches this skill metadata.
- Evaluate exit-strategies before installing it in an agent workflow
- automation
- Finance and quant workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
92
Install handoff is available.
- npx skills add agiprolabs/claude-trading-skills --skill exit-strategies
Install command safety
92
standard package or runtime install path
- npx skills add agiprolabs/claude-trading-skills --skill exit-strategies
Trust score
69
Potentially useful, but at least one trust signal needs human inspection.
- Manual review
- 345 GitHub stars
- MIT
Audit score
76
Needs review
- Financial research output is not financial advice; require human review before any live investment decision
Agent safety gate
48
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- Test manually in an isolated workspace and compare against safer alternatives.
- High-risk permission hints: Secrets or environment access
License clarity
86
MIT
- MIT
Permission surface
74
secrets or environment access
- Network access: medium
- Filesystem access: medium
- Secrets or environment access: high
Validation plan
What the agent should do next
- 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
- 2Install in an isolated workspace or sandbox with no production secrets available.
- 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
- 4Compare the selected skill against at least one alternative when the eval status is review or failed.
- 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 lacks an explicit 'Limitations' or 'Safety' section, though it does mention that scripts are for informational analysis only.
- High-risk permission hints: Secrets or environment access
- Financial research output is not financial advice; require human review before any live investment decision
- The documentation excerpt is truncated in the review, but the full file appears comprehensive based on the provided content.
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
warn76
Public metadata needs stronger README/SKILL.md context
Recent maintenance
pass88
2mo since push
Alternatives available
pass82
Alternative skills are available for comparison.