CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-coordinator-swarm-init

Agent skill for coordinator-swarm-init - invoke with $agent-coordinator-swarm-init

51

2.80x
Quality

29%

Does it follow best practices?

Impact

87%

2.80x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-coordinator-swarm-init/SKILL.md

The canonical home for this skill is agent-coordinator-swarm-init in ruvnet/claude-flow

SKILL.md
Quality
Evals
Security

Quality

Content

38%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a reasonable high-level outline of a swarm-initialization agent but is short on executable guidance and lacks validation checkpoints in its memory-coordination workflow. The duplicated YAML block in the body and absence of any bundle files further weaken its structure.

Suggestions

Remove the spurious second YAML frontmatter block (lines 6-31) from the markdown body.

Add concrete executable commands or a runnable example for topology selection and resource allocation rather than abstract descriptions.

Insert explicit validation/verification checkpoints into the memory-coordination protocol (e.g., verify the status was written before proceeding) to support the feedback-loop requirement.

DimensionReasoningScore

Conciseness

The body is mostly compact bullet lists, but it carries padded emphasis ('MANDATORY', 'ENFORCES', 'VERIFIES', emoji) and a duplicated spurious YAML frontmatter block (lines 6-31), fitting the score-3 anchor of 'mostly efficient but includes some unnecessary content that could be tightened'.

3 / 5

Actionability

Most sections give only high-level descriptions ('Allocates compute resources', 'Establishes message passing protocols') with no concrete commands or executable steps, matching the score-2 anchor of 'minimal concrete guidance; high-level hints but missing specific steps'; only the npx hook snippets provide any executable detail.

2 / 5

Workflow Clarity

The mandatory memory-coordination protocol lists sequenced steps, but there are no validation checkpoints or feedback loops for these memory operations, and the error-handling section is a generic bullet list, matching the score-3 anchor of 'steps listed but validation gaps; checkpoints missing'.

3 / 5

Progressive Disclosure

It is a single monolithic file with no bundle references and an inlined spurious YAML block that should not be in the body, fitting the score-2 anchor of 'minimal structure; content that clearly belongs in separate files is inlined'.

2 / 5

Total

10

/

20

Passed

Description

20%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is boilerplate generated from the skill name with no concrete capability statement, no natural user-facing trigger terms, and no 'Use when' guidance. It reads as a placeholder rather than a meaningful skill description.

Suggestions

Replace the boilerplate with a concrete statement of what the skill does, e.g. 'Initializes and configures agent swarms: selects topology, allocates resources, and sets up memory coordination.'

Add an explicit trigger clause such as 'Use when setting up a multi-agent swarm, choosing a topology, or coordinating shared memory between agents.'

Drop the technical 'invoke with $agent-coordinator-swarm-init' token in favor of natural phrasing users would actually say.

DimensionReasoningScore

Specificity

The phrase 'Agent skill for coordinator-swarm-init' names the domain but provides zero concrete actions, matching the score-2 anchor 'Names the domain but actions are minimal or generic'; it falls above the score-1 entirely-vague anchor because it does name a specific domain.

2 / 5

Completeness

It offers only a vague 'what' ('Agent skill for coordinator-swarm-init') and no 'when'/'Use when' clause at all, matching the score-2 anchor of 'a vague what and no when'; per the missing-trigger-clause guidance it is correctly capped below 3.

2 / 5

Trigger Term Quality

The only keyword is the technical invocation token 'invoke with $agent-coordinator-swarm-init', with no natural phrases a user would actually say, matching the score-1 anchor of 'only technical jargon or entirely generic language'.

1 / 5

Distinctiveness Conflict Risk

The templated form 'Agent skill for X - invoke with $X' is boilerplate that could apply to any agent skill, giving very broad overlap risk as in the score-2 anchor; it is slightly more specific than score-1 only because of the unique coordinator-swarm-init name.

2 / 5

Total

7

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ruvnet/ruflo
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.