OpenAgentSkill
GitHub200+

Pre-install eval

dart-best-practices 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
69
Eval report
72
Trust
76
Audit
56
Agent safety

do not auto install

Install path: No install command or repository handoff is available.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate dart-best-practices before installing it in an agent workflow
  • automation
  • Coding agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

20

fail

No install command or repository handoff is available.

Install command safety

92

pass

standard package or runtime install path

Trust score

72

warn

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

  • Strong shortlist
  • 144 GitHub stars
  • Apache-2.0

Audit score

76

fail

Risky

  • Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required

Agent safety gate

56

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

Apache-2.0

  • Apache-2.0

Permission surface

88

pass

database access

  • Network access: medium
  • Filesystem access: medium
  • Database 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
  • The skill is relatively narrow, covering only two best practices (multi-line strings and line length).
  • Audit risk risky exceeds max_risk=medium
  • Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
  • The parsed description in the metadata appears as '|-' due to YAML block scalar handling, but the actual description is clear in the frontmatter.

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.