Star0

Pre-install eval

Apm 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
83
Eval
83
Trust
90
Audit
66
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 Apm before installing it in an agent workflow
  • agent-frameworks
  • Coding agents workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add microsoft/apm

Install command safety

92

pass

standard package or runtime install path

  • npx skills add microsoft/apm

Trust score

83

pass

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

  • Strong shortlist
  • 2.9K GitHub stars
  • MIT

Audit score

90

pass

Safe to try

  • Documentation summary is thin

Agent safety gate

66

warn

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

  • Require human approval before installing into a real workspace.
  • High-risk permission hints: Shell or command execution

License clarity

86

pass

MIT

  • MIT

Permission surface

76

warn

shell or command execution

  • Shell or command execution: high
  • 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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • High-risk permission hints: Shell or command execution
  • Documentation summary is thin
  • README/SKILL.md completeness: Public metadata needs stronger README/SKILL.md context

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

fail

50

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

12d since push

Alternatives available

pass

82

Alternative skills are available for comparison.