Star200+

Pre-install eval

swarm-coding 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
62
Eval report
61
Trust
71
Audit
39
Agent safety

do not auto install

Permission surface: shell or command execution, filesystem or document access

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate swarm-coding before installing it in an agent workflow
  • research
  • Testing and QA workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add danicat/skills --skill swarm-coding

Install command safety

92

pass

standard package or runtime install path

  • npx skills add danicat/skills --skill swarm-coding

Trust score

61

warn

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

  • Manual review
  • 16 GitHub stars
  • Apache-2.0

Audit score

71

warn

Needs review

  • Dependency or permission surface needs review

Agent safety gate

39

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

Apache-2.0

  • Apache-2.0

Permission surface

36

fail

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • 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 references specific agent framework tools (e.g., define_subagent, invoke_subagent, ask_question) without clarifying that these are environment-specific, which may limit portability.
  • No OpenAgentSkill engagement data yet
  • High-risk permission hints: Shell or command execution

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.