agent-automation-smart-agent
Agent skill for automation-smart-agent - invoke with $agent-automation-smart-agent
38
Quality
3%
Does it follow best practices?
Impact
99%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-automation-smart-agent/SKILL.mdQuality
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 an invocation command without explaining what the skill does, when to use it, or any distinguishing characteristics. The term 'automation-smart-agent' is meaningless internal naming that gives Claude no basis for selecting this skill appropriately.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Automates browser interactions, schedules recurring tasks, orchestrates multi-step workflows').
Include an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to automate repetitive tasks, schedule jobs, or create workflows').
Replace the generic 'automation' framing with specific domains or capabilities to distinguish from other automation-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for automation-smart-agent' 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 only information provided is how to invoke it ('$agent-automation-smart-agent'), not its purpose or triggers. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. 'automation-smart-agent' is technical jargon/internal naming, not terms like 'automate tasks', 'run scripts', or specific automation domains. | 1 / 3 |
Distinctiveness Conflict Risk | 'Automation' is extremely generic and could conflict with any skill involving automated processes. There are no distinguishing features or specific triggers to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
7%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 product specification or design document rather than actionable instructions for Claude. It extensively describes what an intelligent agent coordinator would do conceptually but provides zero executable code, no actual commands, and no concrete steps for implementation. The content assumes Claude needs to understand abstract concepts like 'capability matching' and 'predictive spawning' rather than providing the actual implementation.
Suggestions
Replace all pseudocode blocks with actual executable code showing how to spawn agents, match capabilities, and coordinate tasks
Add a concrete 'Quick Start' section with copy-paste ready commands for basic agent coordination
Remove conceptual explanations (ML integration diagrams, flowcharts) and replace with working implementation examples
Add explicit step-by-step workflow with validation checkpoints for spawning and coordinating agents
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive conceptual explanations Claude already knows. Filled with abstract diagrams, flowcharts, and descriptions of ML concepts without any executable implementation. The 'Machine Learning Integration' section describes what models would do without providing any actual code. | 1 / 3 |
Actionability | No executable code or concrete commands anywhere. All examples are pseudocode or abstract descriptions like 'Automatically spawns: Architect, Refactoring Specialist...' without showing HOW to actually spawn agents. The JavaScript and Python blocks are conceptual diagrams, not runnable code. | 1 / 3 |
Workflow Clarity | No clear step-by-step process for actually using this skill. Describes what the system does conceptually but never explains how to invoke it, what commands to run, or how to validate results. The 'Usage Examples' show inputs but not the actual execution steps. | 1 / 3 |
Progressive Disclosure | Content is organized into logical sections with headers, but it's a monolithic wall of conceptual text. No references to external files for detailed implementation. The structure exists but contains too much inline content that describes rather than instructs. | 2 / 3 |
Total | 5 / 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.
- Repository
- ruvnet/claude-flow
- Commit
b2618f9
- 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.