OpenAgentSkill
GitHub200+

Pre-install eval

booth-giveaway-planner 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
73
Eval report
73
Trust
78
Audit
66
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 booth-giveaway-planner before installing it in an agent workflow
  • other
  • Sales and CRM workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add LensmorOfficial/trade-show-skills --skill booth-giveaway-planner

Install command safety

92

pass

standard package or runtime install path

  • npx skills add LensmorOfficial/trade-show-skills --skill booth-giveaway-planner

Trust score

73

warn

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

  • Strong shortlist
  • 48 GitHub stars
  • MIT

Audit score

78

warn

Needs review

  • No explicit security boundary statement, though the skill is purely advisory and contains no tool execution or external calls.

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.
  • No explicit security boundary statement, though the skill is purely advisory and contains no tool execution or external calls.

License clarity

86

pass

MIT

  • MIT

Permission surface

100

pass

no high-risk permission surface in public metadata

  • 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
  • production agents without a repository review
  • Low GitHub adoption signal
  • No explicit security boundary statement, though the skill is purely advisory and contains no tool execution or external calls.
  • Related skills mentioned in handoff are not included or path-resolved, which could create friction in environments where only this skill directory is installed.
  • Quality score needs review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

11d since push

Alternatives available

pass

82

Alternative skills are available for comparison.