agent-worker-specialist
Agent skill for worker-specialist - invoke with $agent-worker-specialist
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-worker-specialist40
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/skillValidation 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 label and invocation command without any explanation of capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a collection of available skills.
Suggestions
Add concrete actions describing what the worker-specialist actually does (e.g., 'Delegates complex tasks to specialized sub-agents, coordinates parallel work streams, synthesizes results')
Include a 'Use when...' clause with explicit trigger conditions (e.g., 'Use when tasks require multiple specialized capabilities or parallel processing')
Add natural language keywords users might say when they need this functionality (e.g., 'delegate', 'parallel tasks', 'coordinate', 'multi-step workflow')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for worker-specialist' is completely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | Fails to answer both 'what does this do' and 'when should Claude use it'. The description only provides an invocation syntax with no functional information. | 1 / 3 |
Trigger Term Quality | Contains only technical jargon ('agent skill', 'worker-specialist') and an invocation command. No natural keywords a user would actually say when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'worker-specialist' could mean anything. Without knowing what this skill does, it's impossible to distinguish it from other skills or avoid conflicts. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable framework for a worker agent with concrete MCP memory coordination patterns, but suffers from inconsistent code syntax that isn't directly executable. The workflow lacks explicit validation and error recovery steps critical for a task execution specialist. The content is moderately well-organized but could be more concise and better structured across multiple files.
Suggestions
Fix JavaScript syntax to be executable - the MCP tool calls should use proper function call syntax rather than mixing await with object literals
Add explicit validation checkpoints after task completion (e.g., verify deliverables exist, run sanity checks) before reporting complete status
Include error recovery workflows - what happens when a task fails mid-execution? How should the worker retry or escalate?
Split specialized worker types (Code, Analysis, Testing) into separate reference files to reduce main skill length and improve navigation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity like 'the dedicated executor of the hive mind's will' and repetitive JSON structure patterns. However, it does provide concrete code examples without over-explaining basic concepts. | 2 / 3 |
Actionability | Provides concrete code examples with MCP tool calls, but the JavaScript syntax is inconsistent (mixing await with object literals, using $ in key names ambiguously). The code patterns are illustrative but not directly executable as written. | 2 / 3 |
Workflow Clarity | Work patterns section outlines sequential steps, but lacks explicit validation checkpoints. The 'Dependency Management' section shows checking dependencies but doesn't provide clear error recovery beyond reporting blocked status. Missing feedback loops for task failures. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections (Core Responsibilities, Work Patterns, Quality Standards), but everything is in one monolithic file. The 'Integration Points' section references other agents but doesn't link to their documentation. Could benefit from splitting specialized worker types into separate files. | 2 / 3 |
Total | 8 / 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.