OpenAgentSkill
GitHub200+

Pre-install eval

design-everyday-things 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
75
Eval report
78
Trust
82
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

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate design-everyday-things before installing it in an agent workflow
  • research
  • Design and creative workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add wondelai/skills --skill design-everyday-things

Install command safety

92

pass

standard package or runtime install path

  • npx skills add wondelai/skills --skill design-everyday-things

Trust score

78

warn

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

  • Strong shortlist
  • 2.1K GitHub stars
  • MIT

Audit score

82

pass

Safe to try

  • SKILL.md is truncated in the excerpt; the full file may contain additional content not reviewed.

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.
  • SKILL.md is truncated in the excerpt; the full file may contain additional content not reviewed.

License clarity

86

pass

MIT

  • MIT

Permission surface

100

pass

no high-risk permission surface in public metadata

  • Browser automation: medium
  • 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
  • SKILL.md is truncated in the excerpt; the full file may contain additional content not reviewed.
  • No setup instructions for agents on how to configure or instantiate this skill.
  • Quality score needs review
  • Production credentials, payments, or irreversible account changes without explicit human review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.