Star0

Pre-install eval

RAG Search 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
70
Eval
78
Trust
71
Audit
59
Safety

manual review

Require human approval before installing into a real workspace.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate RAG Search before installing it in an agent workflow
  • data
  • RAG and knowledge workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add thinkany-ai/rag-search

Install command safety

92

pass

standard package or runtime install path

  • npx skills add thinkany-ai/rag-search

Trust score

78

warn

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

  • Strong shortlist
  • 1.2K GitHub stars
  • Apache-2.0

Audit score

71

warn

Needs review

  • Documentation summary is thin

Agent safety gate

59

warn

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

  • Require human approval before installing into a real workspace.
  • Documentation summary is thin

License clarity

86

pass

Apache-2.0

  • Apache-2.0

Permission surface

86

pass

network or browser access

  • 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 require actively maintained dependencies
  • production agents without a repository review
  • Repository looks stale
  • No OpenAgentSkill engagement data yet
  • Documentation summary is thin
  • Repository appears stale

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

fail

50

Public metadata needs stronger README/SKILL.md context

Recent maintenance

fail

38

2y since push

Alternatives available

pass

82

Alternative skills are available for comparison.