OpenAgentSkill
GitHub200+

Pre-install eval

article-magazine 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
78
Eval report
76
Trust
84
Audit
68
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

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate article-magazine before installing it in an agent workflow
  • article
  • Content automation workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add nexu-io/html-anything --skill article-magazine

Install command safety

92

pass

standard package or runtime install path

  • npx skills add nexu-io/html-anything --skill article-magazine

Trust score

76

warn

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

  • Strong shortlist
  • 8.6K GitHub stars
  • Apache-2.0

Audit score

84

warn

Needs review

  • SKILL.md does not explicitly describe the expected input format, output format, or step-by-step workflow for agents using this skill.

Agent safety gate

68

warn

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

  • Require human approval before installing into a real workspace.
  • SKILL.md does not explicitly describe the expected input format, output format, or step-by-step workflow for agents using this skill.

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

100

pass

no high-risk permission surface in public metadata

  • 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 explicitly describe the expected input format, output format, or step-by-step workflow for agents using this skill.
  • No listed limitations or safe operating boundaries; for example, it does not clarify when the template is not suitable or how to handle very long/complex articles.
  • The skill directory contains only SKILL.md and example.md; a dedicated usage or setup section in SKILL.md would improve clarity.
  • Quality score needs review

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

78

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.