Star200+

Pre-install eval

pest-testing 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
68
Eval report
69
Trust
76
Audit
56
Agent safety

do not auto install

Permission surface: secrets or environment access, filesystem or document access

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate pest-testing before installing it in an agent workflow
  • data-analysis
  • Testing and QA workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add promovaweb/specsfy --skill pest-testing

Install command safety

92

pass

standard package or runtime install path

  • npx skills add promovaweb/specsfy --skill pest-testing

Trust score

69

warn

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

  • Manual review
  • 60 GitHub stars
  • MIT

Audit score

76

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

56

warn

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • Test manually in an isolated workspace and compare against safer alternatives.
  • Permission surface may require sandboxing

License clarity

86

pass

MIT

  • MIT

Permission surface

46

fail

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 SKILL.md references 'search-docs' without clarifying if that is an external tool or agent-provided utility; ambiguous dependency might confuse agents.
  • Permission surface may require sandboxing
  • The 'Visual Regression Testing' section appears truncated in the provided excerpt; ensure the full SKILL.md includes complete instructions or examples.
  • Quality score needs review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

1d since push

Alternatives available

pass

82

Alternative skills are available for comparison.