agent-orchestrator-task
Agent skill for orchestrator-task - invoke with $agent-orchestrator-task
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-orchestrator-task38
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 82%
↑ 1.32xAgent success when using this skill
Validation for skill structure
Discovery
0%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 critically deficient across all dimensions. It provides only a technical invocation command without explaining what the skill does, when to use it, or any natural language triggers. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add concrete actions describing what this skill does (e.g., 'Coordinates multi-step workflows, delegates subtasks to specialized agents, tracks task completion status').
Include an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs to break down complex projects, coordinate multiple tasks, or manage workflow dependencies').
Remove or relocate the invocation syntax ('$agent-orchestrator-task') as it provides no value for skill selection and wastes description space.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for orchestrator-task' is completely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | Missing both 'what does this do' and 'when should Claude use it'. The description only provides an invocation command but no functional information or trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains only technical jargon ('orchestrator-task', '$agent-orchestrator-task') that users would never naturally say. No natural keywords or common variations are present. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'orchestrator-task' could apply to virtually any task coordination scenario. No clear niche or distinct triggers to differentiate it from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like conceptual documentation rather than actionable guidance. It extensively describes what a task orchestrator does and lists abstract patterns, but provides no concrete commands, executable code, or specific tool invocations. Claude already understands orchestration concepts - this skill should instead provide specific syntax, memory commands, and concrete examples of how to invoke and coordinate agents.
Suggestions
Replace abstract 'Usage Examples' with concrete, executable examples showing actual agent invocation syntax and memory_store/memory_search commands
Remove explanatory content about what orchestration is and focus on specific commands and tool usage patterns
Add validation checkpoints to task patterns (e.g., 'Verify agent response before proceeding', specific error handling)
Provide copy-paste ready code blocks for common orchestration operations instead of conceptual pseudocode
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude already understands (what task decomposition is, what parallel vs sequential means). Heavy padding with organizational descriptions rather than actionable content. | 1 / 3 |
Actionability | No executable code, commands, or concrete examples. The 'Usage Examples' are just natural language descriptions, and the 'Task Patterns' are abstract pseudocode outlines without any actual implementation guidance. | 1 / 3 |
Workflow Clarity | Task patterns show numbered sequences but lack validation checkpoints, error handling, or feedback loops. No concrete steps for how to actually orchestrate - just conceptual patterns without verification steps. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline in one monolithic file. References to other agents exist but no actual file links or clear navigation to detailed documentation. | 2 / 3 |
Total | 6 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.