Star0

Pre-install eval

System Design Primer 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
89
Eval
89
Trust
89
Audit
73
Safety

manual review

Review the audit page, then allow agent install in a sandboxed workflow.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

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

Install path

92

pass

Install handoff is available.

  • npx skills add donnemartin/system-design-primer

Install command safety

92

pass

standard package or runtime install path

  • npx skills add donnemartin/system-design-primer

Trust score

89

pass

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

  • Production candidate
  • 353K GitHub stars
  • Unknown

Audit score

89

pass

Safe to try

  • License is unclear

Agent safety gate

73

warn

Good audit and safety signals with no high-risk permission hints in public metadata.

  • Review the audit page, then allow agent install in a sandboxed workflow.
  • Safe-to-try audit

License clarity

42

warn

Unknown

  • Unknown

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
  • License is unclear
  • License clarity: Unknown
  • Production credentials, payments, or irreversible account changes without explicit human review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

90

Metadata includes enough usage and workflow context

Recent maintenance

warn

76

3mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.