OpenAgentSkill
GitHub200+

Pre-install eval

privacy-eu 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
73
Eval report
73
Trust
79
Audit
63
Agent safety

do not auto install

Audit score: Risky

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate privacy-eu before installing it in an agent workflow
  • automation
  • Legal and compliance workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add kimlawtech/korean-privacy-terms --skill privacy-eu

Install command safety

92

pass

standard package or runtime install path

  • npx skills add kimlawtech/korean-privacy-terms --skill privacy-eu

Trust score

73

warn

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

  • Strong shortlist
  • 578 GitHub stars
  • Apache-2.0

Audit score

79

fail

Risky

  • Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required

Agent safety gate

63

fail

This skill should not be selected by an agent without explicit human security review.

  • Do not auto-install. Inspect the source, dependencies, and permission surface first.
  • Audit risk exceeds the requested agent policy

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

100

pass

no high-risk permission surface in public metadata

  • 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
  • User-provided interview answers are inserted into MDX templates; without escaping or validation, there is a potential template/content injection risk that could break generated pages or alter legal text.
  • Audit risk risky exceeds max_risk=medium
  • Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
  • The SKILL.md excerpt references many external files (checklists, scripts, templates) that are not shown in the excerpt; reviewers cannot fully verify they exist and are complete in the repository.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

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.