Star200+

Pre-install eval

TokHub 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
82
Eval report
82
Trust
89
Audit
61
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

84

pass

Task wording matches this skill metadata.

  • Evaluate TokHub before installing it in an agent workflow
  • development
  • Workflow automation workflows; OpenAI Agents teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add yaojingang/TokHub

Install command safety

92

pass

standard package or runtime install path

  • npx skills add yaojingang/TokHub

Trust score

82

pass

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

  • Strong shortlist
  • 185 GitHub stars
  • Apache-2.0

Audit score

89

warn

Needs review

  • Dependency or permission surface needs review

Agent safety gate

61

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

  • Require human approval before installing into a real workspace.
  • High-risk permission hints: Secrets or environment access

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

46

fail

secrets or environment access, filesystem or document access

  • Network access: medium
  • Filesystem access: medium
  • Secrets or environment access: high

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
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • High-risk permission hints: Secrets or environment access
  • Dependency or permission surface needs review
  • Permission surface may require sandboxing

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

100

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

21d since push

Alternatives available

pass

82

Alternative skills are available for comparison.