Pre-install eval

openspec-plus-tdd 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.

FailedHigh riskBLOCK Policy
66
Eval report
67
Trust
74
Audit
42
Agent safety

do not auto install

Audit score: Risky

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate openspec-plus-tdd before installing it in an agent workflow
  • research
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add sudokar/openspec-plus --skill openspec-plus-tdd

Install command safety

92

pass

standard package or runtime install path

  • npx skills add sudokar/openspec-plus --skill openspec-plus-tdd

Trust score

67

warn

Potentially useful, but at least one trust signal needs human inspection.

  • Manual review
  • 167 GitHub stars
  • MIT

Audit score

74

fail

Risky

  • Permission surface may require sandboxing

Agent safety gate

42

fail

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

pass

MIT

  • MIT

Permission surface

60

warn

secrets or environment access, filesystem or document access

  • Browser automation: medium
  • Network access: medium
  • Filesystem access: medium

Validation plan

What the agent should do next

  1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
  2. 2Install in an isolated workspace or sandbox with no production secrets available.
  3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
  4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
  5. 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
  • The 'delete it, start over' rule in the Iron Law could be interpreted as authorizing destructive deletion; it should explicitly scope deletion to only code the agent just wrote for the current slice and never pre-existing or unrelated files.
  • Audit risk risky exceeds max_risk=medium
  • High-risk permission hints: Secrets or environment access
  • Permission surface may require sandboxing

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.