spec-first Eval
===============

Status: failed
Score: 55/100
Risk: high
Decision: do_not_auto_install
Policy: block
Reason: Trust score: Sparse or weak trust signals. Treat this as an experimental candidate.

Install:
npx skills add shipshitdev/skills --skill spec-first

Required checks:
- PASS Task fit: Task wording matches this skill metadata.
- PASS Install path: Install handoff is available.
- PASS Install command safety: standard package or runtime install path
- FAIL Trust score: Sparse or weak trust signals. Treat this as an experimental candidate.
- WARN Audit score: Needs review
- FAIL Agent safety gate: This skill should not be selected by an agent without explicit human security review.
- WARN License clarity: Unknown
- FAIL Permission surface: secrets or environment access, shell or command execution

Warnings:
- Audit score: Needs review
- README/SKILL.md completeness: Public metadata needs stronger README/SKILL.md context
- License clarity: Unknown
- High-risk permission hints: Shell or command execution, Secrets or environment access
- License is unclear
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- Financial research output is not financial advice; require human review before any live investment decision
- The SKILL.md mentions a todo.md artifact in the description, but the Creates/Modifies section only lists spec and decision files; clarify whether todo.md is written to disk or exists only as a GitHub Issue body.
- No explicit prerequisites/setup section is present; the workflow assumes gh CLI availability, authentication, and an .agents/memory/ directory convention.
- Repository license is detected as Unknown by GitHub, though plugin.json declares MIT; a LICENSE file should be included for clearer compliance.
- Low GitHub adoption signal

Validation plan:
1. Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. Install in an isolated workspace or sandbox with no production secrets available.
3. Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. Compare the selected skill against at least one alternative when the eval status is review or failed.
5. Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when:
- teams that need a vendor-supported SLA
- production agents without a repository review
- Low GitHub adoption signal
- The SKILL.md mentions a todo.md artifact in the description, but the Creates/Modifies section only lists spec and decision files; clarify whether todo.md is written to disk or exists only as a GitHub Issue body.
- High-risk permission hints: Shell or command execution, Secrets or environment access
- License is unclear
- Dependency or permission surface needs review
- Permission surface may require sandboxing

URLs:
- Skill: https://www.openagentskill.com/skills/shipshitdev-spec-first
- Audit: https://www.openagentskill.com/skills/shipshitdev-spec-first/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=shipshitdev-spec-first