OpenAgentSkill
GitHub200+

Pre-install eval

C2C 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
76
Audit
60
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

94

pass

Task wording matches this skill metadata.

  • Evaluate C2C before installing it in an agent workflow
  • agent-frameworks
  • 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

77

warn

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

  • Strong shortlist
  • 414 GitHub stars
  • Apache-2.0

Audit score

76

warn

Needs review

  • Financial research output is not financial advice; require human review before any live investment decision

Agent safety gate

60

warn

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

  • Skill source structure is not confirmed in the registry. Inspect the source and identify valid skill instructions before proposing an installation. A repository URL or GitHub stars do not prove installability.

License clarity

86

pass

Apache-2.0

  • Apache-2.0

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
  • Financial research output is not financial advice; require human review before any live investment decision
  • Skill source structure is not confirmed in the registry. Inspect the source and identify valid skill instructions before proposing an installation. A repository URL or GitHub stars do not prove installability.
  • Financial research output is not financial advice; require human review before any live investment decision.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

90

Metadata includes enough usage and workflow context

Recent maintenance

warn

62

7mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.