OpenAgentSkill
GitHub200+

Pre-install eval

evo-bgp-analysis 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
68
Eval report
69
Trust
74
Audit
58
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

84

pass

Task wording matches this skill metadata.

  • Evaluate evo-bgp-analysis before installing it in an agent workflow
  • automation
  • Browser automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add Zhang-Henry/CoEvoSkills --skill evo-bgp-analysis

Install command safety

92

pass

standard package or runtime install path

  • npx skills add Zhang-Henry/CoEvoSkills --skill evo-bgp-analysis

Trust score

69

warn

Potentially useful, but at least one trust signal needs human inspection.

  • Manual review
  • 65 GitHub stars
  • Apache-2.0

Audit score

74

warn

Needs review

  • The evaluation functions (evaluate_solution_oscillation and evaluate_solution_route_leak) rely on hardcoded ASNs (65002, 65003) and specific text patterns, which may not generalize to other topologies or solution phrasings.

Agent safety gate

58

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

  • Require human approval before installing into a real workspace.
  • The evaluation functions (evaluate_solution_oscillation and evaluate_solution_route_leak) rely on hardcoded ASNs (65002, 65003) and specific text patterns, which may not generalize to other topologies or solution phrasings.

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

72

warn

filesystem or document access, network or browser 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
  • production agents without a repository review
  • The evaluation functions (evaluate_solution_oscillation and evaluate_solution_route_leak) rely on hardcoded ASNs (65002, 65003) and specific text patterns, which may not generalize to other topologies or solution phrasings.
  • SKILL.md does not explicitly describe the expected schema of input JSON files (e.g., preferences.json, route_events.json), which could lead to misuse.
  • Quality score needs review
  • GitHub adoption: 65 GitHub stars

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

3mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.