Star200+

Pre-install eval

annotator-input-parity-check 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
70
Eval report
71
Trust
77
Audit
61
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

84

pass

Task wording matches this skill metadata.

  • Evaluate annotator-input-parity-check before installing it in an agent workflow
  • security
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add kennethkhoocy/applied-micro-skills --skill annotator-input-parity-check

Install command safety

92

pass

standard package or runtime install path

  • npx skills add kennethkhoocy/applied-micro-skills --skill annotator-input-parity-check

Trust score

71

warn

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

  • Manual review
  • 47 GitHub stars
  • MIT

Audit score

77

warn

Needs review

  • No explicit 'Limitations' section, though the Notes section partially covers boundaries.

Agent safety gate

61

warn

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

  • Require human approval before installing into a real workspace.
  • No explicit 'Limitations' section, though the Notes section partially covers boundaries.

License clarity

86

pass

MIT

  • MIT

Permission surface

86

pass

filesystem or document access

  • 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
  • Low GitHub adoption signal
  • No explicit 'Limitations' section, though the Notes section partially covers boundaries.
  • No OpenAgentSkill engagement data yet
  • The skill description is long but well-structured; could be slightly more concise for quick scanning.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.