OpenAgentSkill
GitHub200+

Pre-install eval

seo-geo 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
45
Eval report
56
Trust
54
Audit
18
Agent safety

do not auto install

Trust score: Sparse or weak trust signals. Treat this as an experimental candidate.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate seo-geo before installing it in an agent workflow
  • security
  • RAG and knowledge workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add org-quicko/skills --skill seo-geo

Install command safety

92

pass

standard package or runtime install path

  • npx skills add org-quicko/skills --skill seo-geo

Trust score

56

fail

Sparse or weak trust signals. Treat this as an experimental candidate.

  • High review required
  • 0 GitHub stars
  • Unknown

Audit score

54

fail

Risky

  • License is unclear

Agent safety gate

18

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

42

warn

Unknown

  • Unknown

Permission surface

36

fail

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
  • Low GitHub adoption signal
  • License inconsistency: repository license is unknown, but plugin.json declares MIT. A clear LICENSE file is missing.
  • Audit risk risky exceeds max_risk=medium
  • High-risk permission hints: Shell or command execution

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

warn

62

7mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.