OpenAgentSkill
GitHub200+

Pre-install eval

Applicant Screening 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
65
Eval report
72
Trust
69
Audit
53
Agent safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate Applicant Screening before installing it in an agent workflow
  • other
  • other workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add claude-office-skills/skills --skill Applicant Screening

Install command safety

92

pass

standard package or runtime install path

  • npx skills add claude-office-skills/skills --skill Applicant Screening

Trust score

72

warn

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

  • Strong shortlist
  • 498 GitHub stars
  • MIT

Audit score

69

warn

Needs review

  • AI review approval is missing

Agent safety gate

53

warn

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • AI review approval is missing

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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • AI review approval is missing
  • Quality score needs review
  • README/SKILL.md completeness: Public metadata needs stronger README/SKILL.md context

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

60

Public metadata needs stronger README/SKILL.md context

Recent maintenance

warn

62

9mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.