Pre-install eval

geo-technical 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
74
Eval report
74
Trust
82
Audit
54
Agent safety

do not auto install

Audit score: Risky

Required gates

Checks an agent must pass before install

Open JSON

Task fit

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate geo-technical before installing it in an agent workflow
  • security
  • Security and compliance workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add zubair-trabzada/geo-seo-claude --skill geo-technical

Install command safety

92

pass

standard package or runtime install path

  • npx skills add zubair-trabzada/geo-seo-claude --skill geo-technical

Trust score

74

warn

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

  • Strong shortlist
  • 10K GitHub stars
  • MIT

Audit score

82

fail

Risky

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

Agent safety gate

54

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

MIT

  • MIT

Permission surface

62

warn

shell or command execution, network or browser 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
  • The skill uses Bash and WebFetch against arbitrary user-supplied URLs; fetched HTML, robots.txt, and headers are untrusted and could contain prompt-injection or malicious instructions.
  • Audit risk risky exceeds max_risk=medium
  • High-risk permission hints: Shell or command execution
  • Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

94

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.