agent-v3-queen-coordinator

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

6.25x

Quality

Does it follow best practices?

Impact

100%

6.25x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-v3-queen-coordinator/SKILL.md

Quality

Discovery

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 a label and invocation command with zero functional content. It fails on every dimension because it does not describe what the skill does, when to use it, or include any natural trigger terms. It would be impossible for Claude to correctly select this skill from a list of available skills.

Suggestions

Add a clear statement of what the skill does with specific concrete actions (e.g., 'Coordinates task distribution across multiple sub-agents for parallel processing').

Add an explicit 'Use when...' clause with natural trigger terms that describe the situations or user requests that should activate this skill.

Replace the internal project name with descriptive language that conveys the skill's purpose, and move the invocation syntax to a separate field or append it after the functional description.

Dimension	Reasoning	Score
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 the invocation command, providing no functional or contextual information.	1 / 3
Trigger Term Quality	There are no natural keywords a user would say. 'v3-queen-coordinator' is internal jargon/a project name, and 'invoke with $agent-v3-queen-coordinator' is a technical invocation instruction, not a trigger term.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it provides no distinguishing characteristics. Without knowing what the skill does, it could conflict with anything or nothing — Claude has no basis for selecting it appropriately.	1 / 3
	Total	4 / 12 Passed

Implementation

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 high-level project plan or README rather than an actionable skill for Claude. It describes what 15 agents should accomplish and the timeline, but provides zero concrete guidance on how the Queen Coordinator should actually orchestrate work—no commands for creating/assigning GitHub issues, no coordination protocols, no conflict resolution steps, no concrete examples of agent communication. The hooks in the frontmatter contain more actionable content than the body itself.

Suggestions

Add concrete, executable coordination workflows: e.g., how to create GitHub issues for agents, how to check agent status, how to resolve conflicts between agents, with specific commands and examples.

Replace the abstract phase descriptions with step-by-step orchestration procedures including validation checkpoints (e.g., 'Before moving to Phase 2, verify all Phase 1 PRs are merged and CI passes').

Add specific examples of coordination actions: sample GitHub issue templates, agent assignment commands, status check procedures, and escalation protocols with concrete code/CLI commands.

Reference external files for detailed agent specifications and ADR documents rather than listing abstract phase descriptions inline (e.g., 'See AGENTS.md for individual agent capabilities, ADR-INDEX.md for implementation details').

Dimension	Reasoning	Score
Conciseness	The content is heavily padded with organizational/planning information (agent topology diagrams, phase timelines, success metrics) that describe project management rather than providing actionable instructions Claude can execute. Much of this is conceptual context that doesn't tell Claude what to actually do.	1 / 3
Actionability	There are no concrete commands, executable code, or specific step-by-step instructions for Claude to follow. The content describes a project structure and goals but never tells Claude how to coordinate agents, create issues, manage workflows, or perform any specific task. It reads like a project overview document, not an actionable skill.	1 / 3
Workflow Clarity	While phases are listed, there are no actual workflow steps, no validation checkpoints, no error handling, and no concrete sequences Claude should follow when orchestrating agents. The phases describe what agents should work on but not how the Queen Coordinator should manage them.	1 / 3
Progressive Disclosure	The content has some structural organization with clear sections (Core Mission, Agent Topology, Implementation Phases, Success Metrics), but there are no references to external files for detailed agent specifications, ADR documents, or coordination protocols. Everything is inline but lacks the depth needed.	2 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Commit: 398f7c2

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.