CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-queen-coordinator

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

53

2.93x
Quality

30%

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

43%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 body is a role persona document with concrete memory-key payloads but non-executable tool-call pseudocode and no real workflow sequencing or validation checkpoints. Its structure is navigable, yet the stray duplicate frontmatter block and monolithic inline content limit organization quality.

Suggestions

Remove the duplicate YAML frontmatter block at the top of the body — it is malformed (a second '---' delimited block inside the markdown) and confuses parsing.

Convert the mcp__claude-flow__memory_usage pseudocode blocks into actual executable tool-call syntax or a concrete script (e.g., in scripts/) so the guidance is copy-paste ready.

Add an explicit startup/operation sequence with validation checkpoints (e.g., establish status → verify memory write → issue directives → check compliance → handle non-response), including a validate-fix-retry loop for directive issuance.

DimensionReasoningScore

Conciseness

The body is mostly compact lists and memory-store code blocks, but padded with persona fluff ('sovereign intelligence', 'royal decrees', 'Foster hive loyalty', 'coup prevention mechanisms') and redundant sections (Governance Protocols vs. Delegation Patterns overlap). Mostly efficient but could be tightened — anchor 3, not 4, because the fluff and redundancy go beyond minor trimmable instances.

3 / 5

Actionability

The mcp__claude-flow__memory_usage blocks give concrete payloads (keys, namespaces, JSON values) but are pseudocode — invalid JavaScript, not executable commands — and the protocol sections ('Issue directive → Monitor compliance → Evaluate results') are high-level without execution detail. Some concrete guidance but incomplete, matching the pseudocode anchor.

3 / 5

Workflow Clarity

Only rough sequences exist ('Issue directive → Monitor compliance → Evaluate results'; 'EVERY 2 MINUTES issue status report') with many gaps: no startup ordering, no validation checkpoints, and vague bullets ('Byzantine fault tolerance', 'Coup prevention mechanisms') with no steps. Directive issuance to all agents is a batch operation with no validate/verify feedback loop, which caps the score at 3; the pervasive gaps place it at 2.

2 / 5

Progressive Disclosure

Sections are clearly headed and there are no broken references, but the skill is a monolithic ~200-line file where governance modes, delegation patterns, and emergency protocols could live in separate reference files, and a malformed duplicate YAML frontmatter block sits at the top of the body. Some structure but content that should be separate is inline — anchor 3, not 4, due to the stray frontmatter block and monolithic organization.

3 / 5

Total

11

/

20

Passed

Description

16%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 a placeholder-quality label: it names the skill but describes no capabilities and gives no guidance on when to invoke it. It reads as scaffolding rather than a usable trigger description.

Suggestions

Replace the description with concrete capabilities, e.g. 'Orchestrates hierarchical swarm operations: issues directives, allocates compute/memory resources across agents, monitors hive coherence, and manages succession.'

Add an explicit 'Use when...' clause with natural trigger phrases users would actually say (e.g., 'Use when coordinating multi-agent swarms, allocating agent resources, or establishing hive hierarchy').

Remove the invocation token '$agent-queen-coordinator' from the description; it adds no trigger value and wastes description space.

DimensionReasoningScore

Specificity

The description is 'Agent skill for queen-coordinator - invoke with $agent-queen-coordinator' — a bare label with no action verbs or concrete capabilities, matching the anchor for entirely vague, no concrete actions. It does not reach anchor 2 because even a minimal/generic action verb is absent.

1 / 5

Completeness

It has a vague 'what' ('Agent skill for queen-coordinator') and no 'when' guidance at all — exactly the anchor-2 example pattern. It cannot score 3 because the 'what' is not clear (no described capabilities), and the missing 'Use when...' clause caps it at 3 regardless.

2 / 5

Trigger Term Quality

No natural keywords a user would say; the only terms are the technical invocation token '$agent-queen-coordinator' and the generic phrase 'Agent skill for'. This matches the anchor for only technical jargon or entirely generic language.

1 / 5

Distinctiveness Conflict Risk

It names a specific hive role ('queen-coordinator'), which is somewhat distinct, but sibling agent skills in the same swarm (e.g., collective-intelligence-coordinator) would overlap and nothing describes what distinguishes this skill's triggers. Somewhat specific but overlap risk remains.

3 / 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.

Validation — 16 / 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.