Pre-install eval
blockchain-forensics 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.
do not auto install
Audit score: Risky
Required gates
Checks an agent must pass before install
Task fit
84
Task wording matches this skill metadata.
- Evaluate blockchain-forensics before installing it in an agent workflow
- security
- Research agents workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
92
Install handoff is available.
- npx skills add forefy/.context --skill blockchain-forensics
Install command safety
92
standard package or runtime install path
- npx skills add forefy/.context --skill blockchain-forensics
Trust score
69
Potentially useful, but at least one trust signal needs human inspection.
- Manual review
- 144 GitHub stars
- MIT
Audit score
74
Risky
- Financial research output is not financial advice; require human review before any live investment decision
Agent safety gate
42
This skill should not be selected by an agent without explicit human security review.
- Do not auto-install. Inspect the source, dependencies, and permission surface first.
- Audit risk exceeds the requested agent policy
License clarity
86
MIT
- MIT
Permission surface
62
secrets or environment access, database 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 does not explicitly state operational safety boundaries such as avoiding automated command execution, opening untrusted links/attachments, or handling malicious artifacts only in isolated environments.
- No OpenAgentSkill engagement data yet
- Audit risk risky exceeds max_risk=medium
- High-risk permission hints: Secrets or environment access
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
pass86
Metadata includes enough usage and workflow context
Recent maintenance
pass88
2mo since push
Alternatives available
info55
No close alternatives were found in the current shortlist.