Star200+

Pre-install eval

angularjs-unit-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
55
Eval report
57
Trust
69
Audit
21
Agent safety

do not auto install

Trust score: Sparse or weak trust signals. Treat this as an experimental candidate.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate angularjs-unit-testing before installing it in an agent workflow
  • coding-agents
  • Browser automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add greedychipmunk/agent-skills --skill angularjs-unit-testing

Install command safety

92

pass

standard package or runtime install path

  • npx skills add greedychipmunk/agent-skills --skill angularjs-unit-testing

Trust score

57

fail

Sparse or weak trust signals. Treat this as an experimental candidate.

  • High review required
  • 14 GitHub stars
  • MIT

Audit score

69

warn

Needs review

  • Dependency or permission surface needs review

Agent safety gate

21

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.
  • Metadata combines secrets access with shell or command execution

License clarity

86

pass

MIT

  • MIT

Permission surface

18

fail

secrets or environment access, shell or command execution

  • Shell or command execution: high
  • Browser automation: medium
  • Network 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
  • Low GitHub adoption signal
  • The SKILL.md excerpt appears truncated at 'Test Organization' – ensure the full document is present and complete.
  • 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

warn

70

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

1d since push

Alternatives available

pass

82

Alternative skills are available for comparison.