OpenAgentSkill
GitHub200+

Pre-install eval

cre-legal 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
67
Trust
74
Audit
58
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 cre-legal before installing it in an agent workflow
  • research
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add ahacker-1/cre-agent-skills --skill cre-legal

Install command safety

92

pass

standard package or runtime install path

  • npx skills add ahacker-1/cre-agent-skills --skill cre-legal

Trust score

67

warn

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

  • Manual review
  • 92 GitHub stars
  • Apache-2.0

Audit score

74

fail

Risky

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

Agent safety gate

58

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

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
  • SKILL.md does not include explicit safety boundaries for handling untrusted content inside uploaded legal documents, which could contain injected instructions.
  • Audit risk risky exceeds max_risk=medium
  • Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
  • The skill is positioned for legal review but does not include a clear 'not legal advice' disclaimer or limitation statement in the provided excerpt.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.