OpenAgentSkill
GitHub200+

Pre-install eval

guideline-writing 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
65
Eval report
67
Trust
73
Audit
41
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

94

pass

Task wording matches this skill metadata.

  • Evaluate guideline-writing before installing it in an agent workflow
  • design-creative
  • Design and creative workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add alfadur7/llm-wiki-newsroom --skill guideline-writing

Install command safety

92

pass

standard package or runtime install path

  • npx skills add alfadur7/llm-wiki-newsroom --skill guideline-writing

Trust score

67

warn

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

  • Manual review
  • 82 GitHub stars
  • MIT

Audit score

73

warn

Needs review

  • SKILL.md is more of a craft/style guide than a step-by-step runnable workflow; it lacks an explicit setup, input/output contract, and concrete worked example.

Agent safety gate

41

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: Shell or command execution

License clarity

86

pass

MIT

  • MIT

Permission surface

62

warn

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • Browser automation: medium
  • Network 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 is more of a craft/style guide than a step-by-step runnable workflow; it lacks an explicit setup, input/output contract, and concrete worked example.
  • High-risk permission hints: Shell or command execution
  • The blind review protocol section appears truncated in the provided excerpt, so the complete procedure is not fully demonstrated in SKILL.md alone.
  • 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.