OpenAgentSkill
GitHub200+

Pre-install eval

vllm-feature-design 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
69
Eval report
73
Trust
75
Audit
59
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

94

pass

Task wording matches this skill metadata.

  • Evaluate vllm-feature-design before installing it in an agent workflow
  • design-creative
  • Document processing workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add shen-shanshan/vllm-dev-skills --skill vllm-feature-design

Install command safety

92

pass

standard package or runtime install path

  • npx skills add shen-shanshan/vllm-dev-skills --skill vllm-feature-design

Trust score

73

warn

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

  • Strong shortlist
  • 20 GitHub stars
  • Apache-2.0

Audit score

75

warn

Needs review

  • Low GitHub adoption signal

Agent safety gate

59

warn

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

  • Require human approval before installing into a real workspace.
  • Low GitHub adoption signal

License clarity

86

pass

Apache-2.0

  • Apache-2.0

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
  • AI review approval is missing
  • Quality score needs review
  • GitHub adoption: 20 GitHub stars

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

2d since push

Alternatives available

pass

82

Alternative skills are available for comparison.