OpenAgentSkill
GitHub200+

Pre-install eval

bse-mapping 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
64
Eval report
64
Trust
72
Audit
48
Agent safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate bse-mapping before installing it in an agent workflow
  • data-analysis
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add FTShare-Lab/FTShare-skill --skill bse-mapping

Install command safety

92

pass

standard package or runtime install path

  • npx skills add FTShare-Lab/FTShare-skill --skill bse-mapping

Trust score

64

warn

Potentially useful, but at least one trust signal needs human inspection.

  • Manual review
  • 62 GitHub stars
  • MIT

Audit score

72

warn

Needs review

  • SKILL.md lacks details on output format, error handling, and example usage.

Agent safety gate

48

warn

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • Test manually in an isolated workspace and compare against safer alternatives.
  • High-risk permission hints: Shell or command execution

License clarity

86

pass

MIT

  • MIT

Permission surface

62

warn

shell or command execution, network or browser access

  • Shell or command execution: high
  • 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
  • SKILL.md lacks details on output format, error handling, and example usage.
  • No OpenAgentSkill engagement data yet
  • High-risk permission hints: Shell or command execution
  • handler.py has no docstrings or comments explaining the safe_urlopen logic.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

60

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

88

2mo since push

Alternatives available

info

55

No close alternatives were found in the current shortlist.