Pre-install eval
optimize 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
Install path: No install command or repository handoff is available.
Required gates
Checks an agent must pass before install
Task fit
84
Task wording matches this skill metadata.
- Evaluate optimize before installing it in an agent workflow
- research
- Research agents workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
20
No install command or repository handoff is available.
Install command safety
92
standard package or runtime install path
Trust score
65
Potentially useful, but at least one trust signal needs human inspection.
- Manual review
- 42 GitHub stars
- Apache-2.0
Audit score
71
Needs review
- Permission surface may require sandboxing
Agent safety gate
39
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- The tracked source changed or could not be synchronized. Review the current source before installing.
License clarity
86
Apache-2.0
- Apache-2.0
Permission surface
48
secrets or environment access, filesystem or document 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
- Low GitHub adoption signal
- The skill instructs to override training data with specific recommendations, which may be opinionated but is not a security risk.
- High-risk permission hints: Secrets or environment access
- Permission surface may require sandboxing
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
pass86
Metadata includes enough usage and workflow context
Recent maintenance
pass88
1mo since push
Alternatives available
pass82
Alternative skills are available for comparison.