agent-automation-smart-agent
Agent skill for automation-smart-agent - invoke with $agent-automation-smart-agent
35
0%
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 is an extremely weak description that provides essentially no useful information for skill selection. It reads as a placeholder or auto-generated stub, containing only an invocation command and a generic label. It fails on every dimension: no concrete actions, no natural trigger terms, no 'what' or 'when' guidance, and no distinctiveness.
Suggestions
Replace the entire description with concrete actions the skill performs (e.g., 'Automates browser interactions, runs scheduled tasks, orchestrates multi-step workflows' — whatever the skill actually does).
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 asks to automate repetitive tasks, schedule jobs, or create workflow pipelines').
Remove the invocation syntax ('invoke with $agent-automation-smart-agent') from the description — this is implementation detail, not selection guidance — and replace it with domain-specific keywords users would naturally use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for automation-smart-agent' is entirely vague and abstract, providing no information about 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 how to invoke it ('$agent-automation-smart-agent') without explaining its purpose or trigger conditions. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say. 'automation-smart-agent' is technical jargon/an internal identifier, not something a user would naturally mention in a request. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'automation' is extremely generic and could overlap with virtually any automation-related skill. There is nothing distinctive about this description to differentiate it from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a conceptual design document or marketing overview rather than an actionable skill. It describes what an intelligent agent coordinator would theoretically do but provides zero executable instructions, commands, or concrete implementation details. Every section is abstract and descriptive, explaining concepts Claude already understands while failing to provide the specific guidance needed to actually perform any task.
Suggestions
Replace all pseudocode blocks with actual executable commands or code that Claude can run to spawn, manage, and coordinate agents in the specific system being used.
Add a concrete quick-start workflow with numbered steps, real commands, and validation checkpoints (e.g., 'Run `swarm status` to verify agents spawned correctly').
Remove conceptual sections like 'Machine Learning Integration' and 'Intelligence Features' that describe abstract capabilities without actionable instructions, and replace with specific tool invocations and parameters.
Split advanced content (multi-objective optimization, adaptive strategies) into separate referenced files and keep SKILL.md focused on the core spawning and coordination workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with conceptual descriptions Claude already understands. Sections like 'Intelligence Features', 'Machine Learning Integration', and 'Best Practices' describe abstract concepts without providing any executable or actionable content. The entire document reads like a product brochure rather than a skill instruction. | 1 / 3 |
Actionability | No concrete, executable code or commands anywhere. All code blocks are pseudocode or conceptual diagrams (e.g., 'Task Requirements → Capability Analysis → Agent Selection'). The 'python' and 'javascript' blocks are abstract descriptions, not runnable code. There are no actual commands for spawning agents, no API calls, no real tool usage instructions. | 1 / 3 |
Workflow Clarity | Despite describing multi-step coordination processes, there are no clear sequential workflows with validation checkpoints. The 'Automation Patterns' section lists conceptual steps but provides no actual execution sequence, no error handling, and no validation steps. The failure recovery section is entirely abstract. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline despite being over 150 lines. There's no clear hierarchy between quick-start essentials and advanced features—everything is presented at the same level of (non-)detail with no navigation aids or file references. | 1 / 3 |
Total | 4 / 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/ruflo
- Commit
ccb062f
- 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.