Star200+

Pre-install eval

accessible-html 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
66
Eval report
68
Trust
72
Audit
52
Agent safety

do not auto install

Permission surface: secrets or environment access, filesystem or document access

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate accessible-html before installing it in an agent workflow
  • design-creative
  • GitHub automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add AlemTuzlak/skills --skill accessible-html

Install command safety

92

pass

standard package or runtime install path

  • npx skills add AlemTuzlak/skills --skill accessible-html

Trust score

68

warn

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

  • Manual review
  • 39 GitHub stars
  • Unknown

Audit score

72

warn

Needs review

  • License is unclear

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.
  • License is unclear

License clarity

42

warn

Unknown

  • Unknown

Permission surface

46

fail

secrets or environment access, filesystem or document access

  • 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
  • Low GitHub adoption signal
  • Repository license is unknown; no license file detected. This creates ambiguity about usage rights and redistribution.
  • License is unclear
  • Permission surface may require sandboxing

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

2d since push

Alternatives available

pass

82

Alternative skills are available for comparison.