OpenAgentSkill
GitHub200+

Pre-install eval

design-workflow 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.

FailedHigh riskBLOCK Policy
73
Eval report
77
Trust
80
Audit
52
Agent safety

do not auto install

Audit score: Risky

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate design-workflow before installing it in an agent workflow
  • design-creative
  • Workflow automation workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add rome-os/rome --skill design-workflow

Install command safety

92

pass

standard package or runtime install path

  • npx skills add rome-os/rome --skill design-workflow

Trust score

77

warn

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

  • Strong shortlist
  • 727 GitHub stars
  • MIT

Audit score

80

fail

Risky

  • Permission surface may require sandboxing

Agent safety gate

52

fail

This skill should not be selected by an agent without explicit human security review.

  • Do not auto-install. Inspect the source, dependencies, and permission surface first.
  • Audit risk exceeds the requested agent policy

License clarity

86

pass

MIT

  • MIT

Permission surface

48

fail

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • 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
  • Audit risk risky exceeds max_risk=medium
  • High-risk permission hints: Shell or command execution
  • Permission surface may require sandboxing

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

3d since push

Alternatives available

pass

82

Alternative skills are available for comparison.