OpenAgentSkill
GitHub200+

Pre-install eval

mindmap 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
67
Eval report
69
Trust
74
Audit
58
Agent 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 mindmap before installing it in an agent workflow
  • automation
  • Browser automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add guoliang1114-boop/AriaAI --skill mindmap

Install command safety

92

pass

standard package or runtime install path

  • npx skills add guoliang1114-boop/AriaAI --skill mindmap

Trust score

69

warn

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

  • Manual review
  • 37 GitHub stars
  • MIT

Audit score

74

warn

Needs review

  • The SKILL.md does not define an explicit input/output contract or step-by-step workflow, so an agent must infer how to collect user requirements, structure the map, and present the output.

Agent safety gate

58

warn

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

  • Require human approval before installing into a real workspace.
  • The SKILL.md does not define an explicit input/output contract or step-by-step workflow, so an agent must infer how to collect user requirements, structure the map, and present the output.

License clarity

86

pass

MIT

  • MIT

Permission surface

100

pass

no high-risk permission surface in public metadata

  • Network access: medium
  • Filesystem 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
  • The SKILL.md does not define an explicit input/output contract or step-by-step workflow, so an agent must infer how to collect user requirements, structure the map, and present the output.
  • The metadata.author field is used as promotional content for Markdown Viewer instead of identifying the skill author, and the parsed metadata does not include a top-level author field.
  • There is no limitations section explaining when mind maps are not appropriate or what PlantUML renderer/version is required.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.