Pre-install eval

angular-modern-apis 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.

Needs reviewMedium riskREVIEW Policy
72
Eval report
72
Trust
79
Audit
67
Agent safety

manual review

Require human approval before installing into a real workspace.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate angular-modern-apis before installing it in an agent workflow
  • design-creative
  • Design and creative workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add mgechev/skillgrade --skill angular-modern-apis

Install command safety

92

pass

standard package or runtime install path

  • npx skills add mgechev/skillgrade --skill angular-modern-apis

Trust score

72

warn

Good trust signals with a few areas worth checking before rollout.

  • Strong shortlist
  • 702 GitHub stars
  • MIT

Audit score

79

warn

Needs review

  • SKILL.md does not specify the minimum Angular version required for signal-based inputs, output(), inject(), and built-in control flow.

Agent safety gate

67

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

  • Require human approval before installing into a real workspace.
  • SKILL.md does not specify the minimum Angular version required for signal-based inputs, output(), inject(), and built-in control flow.

License clarity

86

pass

MIT

  • MIT

Permission surface

100

pass

no high-risk permission surface in public metadata

  • 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
  • SKILL.md does not specify the minimum Angular version required for signal-based inputs, output(), inject(), and built-in control flow.
  • SKILL.md lacks explicit limitations or edge cases, such as when legacy APIs may still be necessary or how to handle two-way bindings during migration.
  • The skill describes mandatory coding standards but does not explain the migration workflow, acceptance criteria, or how the examples should be applied to a full codebase.
  • Quality score 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

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.