OpenAgentSkill
GitHub200+

Pre-install eval

better-typography 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
68
Eval report
68
Trust
75
Audit
55
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 better-typography before installing it in an agent workflow
  • coding-agents
  • Coding agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add boraoztunc/skills --skill better-typography

Install command safety

92

pass

standard package or runtime install path

  • npx skills add boraoztunc/skills --skill better-typography

Trust score

68

warn

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

  • Manual review
  • 418 GitHub stars
  • Apache-2.0

Audit score

75

warn

Needs review

  • SKILL.md metadata lacks YAML tags/frameworks fields; not required, but reduces discoverability in some agents.

Agent safety gate

55

warn

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • SKILL.md metadata lacks YAML tags/frameworks fields; not required, but reduces discoverability in some agents.

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

72

warn

filesystem or document access, network or browser 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
  • SKILL.md metadata lacks YAML tags/frameworks fields; not required, but reduces discoverability in some agents.
  • No explicit 'Limitations' section describing when the skill should not be applied or that it only makes recommendations and does not execute code.
  • The skill references sibling skills by name (better-writing, better-accessibility, better-layout, better-colors) without describing fallback behavior when those skills are unavailable.
  • The provided SKILL.md excerpt ends mid-sentence at '### 6. Heading Siz'; if the actual file is truncated, it would be a critical completeness issue, but based on the repository structure this appears to be an excerpt artifact.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

3mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.