CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-v3-queen-coordinator

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

36

6.25x
Quality

0%

Does it follow best practices?

Impact

100%

6.25x

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-v3-queen-coordinator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

0%Scale 1-3

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

This skill reads as a project overview or README rather than an actionable skill for Claude. It describes an ambitious 15-agent swarm coordination system but provides zero concrete instructions on how to actually perform coordination—no commands to run, no decision trees for task assignment, no templates for GitHub issues, and no workflows for cross-agent communication. The extensive YAML frontmatter hooks contain more actionable content than the skill body itself.

Suggestions

Add concrete, executable workflows for the queen coordinator's core tasks: e.g., how to create and assign GitHub issues to agents, how to check agent status, how to resolve conflicts between agents, with specific commands and templates.

Replace the descriptive phase breakdown with actionable decision trees or checklists that Claude can follow when coordinating work—e.g., 'When a new task arrives: 1. Classify by ADR, 2. Check agent availability via `gh issue list --label agent-N`, 3. Create issue with template...'

Add references to ADR documents and agent-specific skill files so Claude can look up detailed specifications when needed, rather than embedding high-level summaries.

Include concrete examples of coordination scenarios (e.g., handling a blocked agent, resolving merge conflicts between agents, escalating issues) with specific commands and expected outputs.

DimensionReasoningScore

Conciseness

The content is heavily padded with organizational diagrams, phase breakdowns, and high-level project management information that Claude doesn't need to act on. The ASCII topology diagram, phase timelines, and success metrics are descriptive rather than instructive. Much of this reads like a project charter, not an actionable skill.

1 / 3

Actionability

There are no concrete commands, executable code, or specific instructions for what Claude should actually do when this skill is invoked. The content describes a project structure and agent topology but never tells Claude how to coordinate agents, create issues, assign work, or perform any specific task. It's entirely descriptive.

1 / 3

Workflow Clarity

While phases are listed, there is no actionable workflow with steps Claude can follow. No validation checkpoints, no decision points, no error handling, and no concrete sequencing of operations. The phases describe what agents should do at a high level but not how the queen coordinator should orchestrate them.

1 / 3

Progressive Disclosure

No bundle files are provided, yet the skill references ADR-001 through ADR-010 without linking to them. There are no references to supporting documents, no links to agent-specific instructions, and no structured navigation. The content is a monolithic block of high-level description with no layered information architecture.

1 / 3

Total

4

/

12

Passed

Description

0%Scale 1-3

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

This description is essentially non-functional. It provides only an internal name and invocation command with zero information about what the skill does, what capabilities it offers, or when it should be used. It would be impossible for Claude to make an informed selection decision based on this description.

Suggestions

Add concrete actions describing what the skill does (e.g., 'Coordinates task distribution across multiple agents, manages parallel workflows, and aggregates results').

Add an explicit 'Use when...' clause with natural trigger terms that describe the scenarios where this skill should be selected.

Replace the internal identifier 'v3-queen-coordinator' with user-facing language that describes the skill's domain and purpose.

DimensionReasoningScore

Specificity

The description contains no concrete actions whatsoever. 'Agent skill for v3-queen-coordinator' is entirely abstract and gives no indication of what the skill actually does.

1 / 3

Completeness

Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an agent skill and how to invoke it, with no functional or trigger information.

1 / 3

Trigger Term Quality

There are no natural keywords a user would say. 'v3-queen-coordinator' is internal jargon with no connection to user intent or natural language queries.

1 / 3

Distinctiveness Conflict Risk

The description is so vague that it provides no basis for distinguishing it from any other skill. Without knowing what it does, Claude cannot reliably select or avoid selecting it.

1 / 3

Total

4

/

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.

Validation11 / 11 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.