OpenAgentSkill
GitHub200+

Pre-install eval

Deploy to Vercel 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
86
Eval report
87
Trust
92
Audit
68
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 Deploy to Vercel before installing it in an agent workflow
  • devops
  • Coding agents workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add vercel-labs/agent-skills --skill deploy-to-vercel

Install command safety

92

pass

standard package or runtime install path

  • npx skills add vercel-labs/agent-skills --skill deploy-to-vercel

Trust score

87

pass

Strong OpenAgentSkill Trust Score across adoption, recent maintenance, license clarity, documentation, dependency/runtime risk, install safety, permission surface, and install availability.

  • Production candidate
  • 33K GitHub stars
  • Source terms (see source)

Audit score

92

pass

Safe to try

  • Deployment can publish external changes; review the target project and production settings before use.

Agent safety gate

68

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: Secrets or environment access

License clarity

86

pass

Source terms (see source)

  • Source terms (see source)

Permission surface

74

warn

secrets or environment access

  • Network access: medium
  • Secrets or environment access: high

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
  • Deployment can publish external changes; review the target project and production settings before use.
  • High-risk permission hints: Secrets or environment access
  • Production credentials, payments, or irreversible account changes without explicit human review
  • Sensitive private data before reviewing repository code, license, and permission surface

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

90

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

4d since push

Alternatives available

pass

82

Alternative skills are available for comparison.