OpenAgentSkill
GitHub200+

Pre-install eval

explain-code 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
70
Eval report
76
Trust
80
Audit
52
Agent safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate explain-code before installing it in an agent workflow
  • coding-agents
  • Coding agents workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add AgnosticUI/agnosticui --skill explain-code

Install command safety

92

pass

standard package or runtime install path

  • npx skills add AgnosticUI/agnosticui --skill explain-code

Trust score

76

warn

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

  • Strong shortlist
  • 828 GitHub stars
  • Apache-2.0

Audit score

80

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

52

warn

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • Test manually in an isolated workspace and compare against safer alternatives.
  • High-risk permission hints: Secrets or environment access

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

60

warn

secrets or environment access, filesystem or document access

  • Network access: medium
  • Filesystem access: medium
  • Secrets or environment access: high

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
  • High-risk permission hints: Secrets or environment access
  • Permission surface may require sandboxing
  • AI review approval is missing

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

70

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

3d since push

Alternatives available

pass

82

Alternative skills are available for comparison.