Pre-install eval
verification-before-completion 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
Agent safety gate: This skill should not be selected by an agent without explicit human security review.
Required gates
Checks an agent must pass before install
Task fit
94
Task wording matches this skill metadata.
- Evaluate verification-before-completion before installing it in an agent workflow
- design-creative
- Design and creative workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
92
Install handoff is available.
- npx skills add DollarDill/beads-superpowers --skill verification-before-completion
Install command safety
92
standard package or runtime install path
- npx skills add DollarDill/beads-superpowers --skill verification-before-completion
Trust score
67
Potentially useful, but at least one trust signal needs human inspection.
- Manual review
- 28 GitHub stars
- MIT
Audit score
74
Needs review
- Dependency or permission surface needs review
Agent safety gate
34
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.
- Metadata combines secrets access with shell or command execution
License clarity
86
MIT
- MIT
Permission surface
36
secrets or environment access, shell or command execution
- Shell or command execution: high
- Network access: medium
- Filesystem access: medium
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
- No explicit mention of how to handle verification commands that themselves could be destructive (e.g., a test that deletes data), though the skill's emphasis on reading output and checking exit codes mitigates this.
- High-risk permission hints: Shell or command execution, Secrets or environment access
- Dependency or permission surface needs review
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
warn76
Public metadata needs stronger README/SKILL.md context
Recent maintenance
pass100
18d since push
Alternatives available
pass82
Alternative skills are available for comparison.