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

Content

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 a high-level architectural overview or design document rather than an actionable skill for Claude. It describes what a task orchestrator conceptually does but never provides concrete instructions, executable code, specific tool invocations, or validation steps. The content is almost entirely abstract description of concepts Claude already understands, making it both verbose and non-actionable.

Suggestions

Replace abstract descriptions with concrete, executable workflows—e.g., show exactly how to use TodoWrite to create a task plan, how to invoke sub-agents, and how to store/retrieve results from memory.

Add specific input/output examples: given a user request like 'build auth system', show the exact task decomposition output format and the specific commands/tool calls to execute each step.

Remove sections that describe concepts Claude already knows (what task decomposition is, what parallel execution means) and replace with project-specific conventions or tool-specific syntax.

Add validation checkpoints to workflows—e.g., after task decomposition, verify all dependencies are satisfiable before proceeding to execution.

Dimension	Reasoning	Score
Conciseness	The content is 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 content could be reduced by 70%+ without losing useful information.	1 / 3
Actionability	The skill provides no executable code, no concrete commands, and no specific implementation details. The 'Task Patterns' are abstract outlines (e.g., 'Requirements Analysis (Sequential)') with no actual steps, tools, or commands. The 'Usage Examples' are just natural language prompts, not demonstrations of how to accomplish anything.	1 / 3
Workflow Clarity	While task patterns list phases, they lack any concrete sequencing details, validation checkpoints, or error recovery steps. There are no actual workflow instructions—just labeled categories like 'Sequential' and 'Parallel' without explaining how to execute, validate, or recover from 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, and several sections (Integration Points, Advanced Features) could be split out. No bundle files exist to reference.	2 / 3
	Total	5 / 12 Passed

Description

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 no information about what the skill does, when it should be used, or what distinguishes it from other skills. It reads as a placeholder rather than a functional description.

Suggestions

Replace the entire description with concrete actions the skill performs, e.g., 'Breaks down complex tasks into subtasks and coordinates their execution across multiple 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 multi-step task coordination, workflow orchestration, or parallel task execution.'

Remove the invocation syntax ('invoke with $agent-orchestrator-task') from the description, as this is implementation detail that doesn't help with skill selection.

Dimension	Reasoning	Score
Specificity	The description provides 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 trigger information.	1 / 3
Trigger Term Quality	The only terms present are 'orchestrator-task' and '$agent-orchestrator-task', which are internal/technical jargon. No natural keywords a user would say are included.	1 / 3
Distinctiveness Conflict Risk	The description is so generic ('agent skill') that it provides no distinguishing characteristics. It could conflict with any other agent-based skill and offers no clear niche.	1 / 3
	Total	4 / 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: 28c81c0

Reviewed: about 20 hours 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.