CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-queen-coordinator

Agent skill for queen-coordinator - invoke with $agent-queen-coordinator

53

2.93x
Quality

28%

Does it follow best practices?

Impact

97%

2.93x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-queen-coordinator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is well-sectioned and offers concrete tool-call templates for swarm coordination, but it is padded with decorative role-play framing, uses placeholder values in non-executable pseudocode, and lacks validation checkpoints. As a monolithic ~200-line file with no references it also misses progressive disclosure.

Suggestions

Remove decorative role-play prose ('sovereign', 'royal', 'hive loyalty') and keep only functional guidance to improve token efficiency.

Replace placeholder JSON values with real, executable MCP tool-call examples or clearly mark them as templates.

Add explicit validation/verification steps (e.g., confirm directive compliance before issuing the next) to the coordination workflow.

DimensionReasoningScore

Conciseness

The body is mostly structured code/data blocks but is padded with decorative role-play prose ('sovereign intelligence at the apex of the hive mind', 'Royal Decrees', 'foster hive loyalty') and verbose JSON.stringify template payloads that could be tightened, matching 'mostly efficient but includes some unnecessary explanation'.

2 / 3

Actionability

It provides concrete mcp__claude-flow__memory_usage calls with specific keys and namespaces, but the stylized non-JS syntax and placeholder/mock values (coherence_score: 0.95, morale: 'high', objectives_completed: ['obj1']) make them templates rather than fully executable code, fitting 'some concrete guidance but incomplete'.

2 / 3

Workflow Clarity

Sequences are present (Command Protocols: 'Issue directive -> Monitor compliance -> Evaluate results') and sections are labeled, but there are no validation/verification checkpoints for batch coordination operations; per the guideline missing validation in such workflows caps workflow clarity at 2.

2 / 3

Progressive Disclosure

No bundle files exist and all content is inline in a single ~200-line file with clear section headings but no external references or file splitting, matching 'some structure but content that should be separate is inline'.

2 / 3

Total

8

/

12

Passed

Description

7%

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 frontmatter description is essentially a label plus invocation hint rather than a capability statement; it omits both concrete actions and trigger guidance. It is distinct as a niche but fails to communicate what the skill does or when to use it.

Suggestions

Replace the description with concrete actions the skill performs (e.g., 'Orchestrates hierarchical agent swarms, allocates resources, and issues coordinated directives').

Add an explicit trigger clause such as 'Use when coordinating a multi-agent hive or centralized swarm workflow'.

Drop the meta-framing 'Agent skill for ... - invoke with $...' which describes packaging rather than capability.

DimensionReasoningScore

Specificity

The description 'Agent skill for queen-coordinator - invoke with $agent-queen-coordinator' names no concrete actions or capabilities, only a label and an invocation hint, matching the 'vague or no actions' anchor.

1 / 3

Completeness

It states neither what the skill concretely does nor when Claude should use it, with no 'Use when...' clause; per the guideline a missing trigger clause caps completeness at 2, and here even the 'what' is absent.

1 / 3

Trigger Term Quality

It contains only the technical token 'queen-coordinator' and an invocation string; no natural phrasing a user would actually say when they need this skill, fitting the 'no natural keywords; technical jargon' anchor.

1 / 3

Distinctiveness Conflict Risk

The 'queen-coordinator' niche is fairly specific and unlikely to collide with unrelated skills, but the description frames it generically as an 'agent skill for X' rather than describing a distinct capability, so it only reaches 'somewhat specific but could overlap'.

2 / 3

Total

5

/

12

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/claude-flow
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.