OpenAgentSkill
GitHub200+

Pre-install eval

shijing-paper-zine 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
73
Trust
76
Audit
56
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

84

pass

Task wording matches this skill metadata.

  • Evaluate shijing-paper-zine before installing it in an agent workflow
  • research
  • Research agents workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add kangarooking/kangarooking-skills --skill shijing-paper-zine

Install command safety

92

pass

standard package or runtime install path

  • npx skills add kangarooking/kangarooking-skills --skill shijing-paper-zine

Trust score

73

warn

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

  • Strong shortlist
  • 568 GitHub stars
  • Unknown

Audit score

76

warn

Needs review

  • License is unclear

Agent safety gate

56

warn

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • License is unclear

License clarity

42

warn

Unknown

  • Unknown

Permission surface

100

pass

no high-risk permission surface in public metadata

  • Browser automation: medium
  • 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
  • Repository license is unknown; no explicit license for the skill or its assets.
  • License is unclear
  • SKILL.md does not state a license or usage terms for the skill itself.
  • Quality score needs review

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.