agent-orchestrator-task

Agent skill for orchestrator-task - invoke with $agent-orchestrator-task

1.32x

Quality

Does it follow best practices?

Impact

82%

1.32x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-orchestrator-task/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 is an extremely weak description that fails on every dimension. It provides no information about what the skill does, when it should be used, or what distinguishes it from other skills. It reads as a placeholder or auto-generated stub rather than a functional description.

Suggestions

Replace the entire description with concrete actions the skill performs, e.g., 'Coordinates multi-step workflows by breaking complex tasks into subtasks and delegating to specialized agents.'

Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected, e.g., 'Use when the user requests a complex task requiring multiple steps, parallel execution, or coordination across different tools.'

Remove the invocation instruction ('invoke with $agent-orchestrator-task') from the description, as it does not help Claude decide when to select this skill and wastes space.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for orchestrator-task' 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 contextual information.	1 / 3
Trigger Term Quality	There are no natural keywords a user would say. 'orchestrator-task' is internal jargon, and 'invoke with $agent-orchestrator-task' is a technical invocation instruction, not a trigger term.	1 / 3
Distinctiveness Conflict Risk	The description is so generic that it provides no distinguishing characteristics. 'Agent skill for orchestrator-task' could overlap with virtually any orchestration or task-management skill.	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 conceptual overview or marketing document rather than an actionable skill file. It describes what a task orchestrator does in abstract terms but provides zero concrete guidance on how Claude should actually perform orchestration—no specific tool calls, no executable code, no concrete examples of task plans or memory operations. The verbose descriptions of concepts like 'task decomposition' and 'dependency management' waste tokens on things Claude already understands.

Suggestions

Replace abstract descriptions with concrete, executable examples showing actual tool invocations (e.g., specific TodoWrite calls for task tracking, memory_store commands for state management, agent invocation syntax).

Add a concrete workflow with validation checkpoints, e.g., 'Step 1: Decompose task using TodoWrite with this format... Step 2: Verify dependencies by checking... Step 3: If blocked, re-plan by...'

Remove sections that explain concepts Claude already knows (what task decomposition is, what parallel execution means) and replace with specific patterns showing exact inputs/outputs.

Add at least one complete end-to-end example showing how to orchestrate a real task, including the specific commands, tool calls, and expected intermediate states.

Dimension	Reasoning	Score
Conciseness	The content is extremely verbose and largely describes abstract concepts Claude already understands (task decomposition, dependency management, parallelization). Most sections are conceptual descriptions rather than actionable instructions, and the entire document reads like a product brochure rather than a skill file.	1 / 3
Actionability	There is no executable code, no concrete commands, and no specific tool invocations. The 'usage examples' are just natural language prompts, and the 'task patterns' are abstract outlines with no actual implementation details. Claude would not know what specific actions to take from this content.	1 / 3
Workflow Clarity	While task patterns list numbered steps, they are entirely abstract (e.g., 'Reproduce + Analyze') with no concrete commands, validation checkpoints, or error recovery steps. There is no clear workflow for how the orchestrator should actually coordinate tasks, invoke other agents, or handle failures.	1 / 3
Progressive Disclosure	The content is organized into logical sections with clear headers, which provides some structure. However, it's a monolithic document with no references to external files for detailed content, and much of the inline content is filler that could be removed entirely rather than split out.	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/claude-flow
Commit: f547cec

Reviewed: 4 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.