agent-workflow-automation
Agent skill for workflow-automation - invoke with $agent-workflow-automation
36
3%
Does it follow best practices?
Impact
95%
6.33xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-workflow-automation/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 essentially a label with an invocation command, providing no useful information about what the skill does, when to use it, or how it differs from other skills. It fails on every dimension due to its extreme vagueness and lack of any concrete detail or trigger guidance.
Suggestions
Replace the generic label with specific concrete actions the skill performs, e.g., 'Automates multi-step workflows by chaining tasks, scheduling jobs, and managing dependencies between pipeline stages.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to automate repetitive tasks, create pipelines, schedule recurring jobs, or orchestrate multi-step processes.'
Specify the domain or type of workflows (e.g., CI/CD, data pipelines, business process automation) to reduce conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Workflow-automation' is abstract and vague—it doesn't specify what kind of workflows, what actions are performed, or what outputs are produced. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no 'Use when...' clause and no meaningful explanation of capabilities. | 1 / 3 |
Trigger Term Quality | The only keyword is 'workflow-automation,' which is overly generic and not a natural phrase users would say. There are no specific trigger terms like 'automate tasks,' 'pipeline,' 'schedule,' or any domain-specific language. | 1 / 3 |
Distinctiveness Conflict Risk | 'Workflow-automation' is extremely generic and could overlap with virtually any automation-related skill. There are no distinct triggers or niche identifiers to differentiate it from other skills. | 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 is an extremely verbose, largely non-actionable document that presents fictional tooling (ruv-swarm, swarm-action) as if it were real executable code. The content is highly repetitive, with multiple sections covering optimization, analysis, and monitoring using slightly different syntax but no real substance. It fails to provide any genuinely executable guidance and lacks validation/error-recovery workflows despite dealing with CI/CD operations.
Suggestions
Replace all fictional 'npx ruv-swarm' commands and 'ruvnet/swarm-action' references with real, executable tools and GitHub Actions that actually exist, or clearly document how to install/build these tools first.
Reduce the content by at least 70% — consolidate the many overlapping sections (optimization, analysis, monitoring, performance) into a single concise workflow with one clear example each.
Add explicit validation checkpoints and error recovery steps to multi-step workflows, especially for deployment and self-healing pipelines.
Move detailed workflow templates and integration examples into separate referenced files, keeping SKILL.md as a concise overview with quick-start guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with massive amounts of repetitive examples. Many sections cover the same concepts (optimization, analysis, monitoring) with slight variations. The content explains things Claude already knows and includes speculative tool invocations (ruv-swarm, mcp__claude-flow) that are essentially pseudocode repeated in multiple forms. The 'Advanced Swarm Workflow Automation' section largely duplicates earlier content in a different syntax. | 1 / 3 |
Actionability | Nearly all code examples reference a fictional tool 'npx ruv-swarm' and fictional GitHub Actions like 'ruvnet/swarm-action@v1' that don't exist as real, executable tools. The mcp__claude-flow invocations use pseudo-JSON syntax that isn't valid for any real tool. Nothing is copy-paste executable — it's aspirational pseudocode dressed up as real commands. | 1 / 3 |
Workflow Clarity | Despite presenting many multi-step workflows, none include validation checkpoints or error recovery steps. The 'Self-Healing CI/CD' section ironically has no actual healing logic. Steps are listed but there's no clear sequence for when things go wrong, no feedback loops, and no verification that previous steps succeeded before proceeding. | 1 / 3 |
Progressive Disclosure | The content has section headers and ends with references to related files (swarm-pr.md, swarm-issue.md, sync-coordinator.md), showing some awareness of progressive disclosure. However, the body itself is a monolithic wall of repetitive examples that should have been split into separate reference files. The inline content is far too long for a SKILL.md overview. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (640 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- ruvnet/claude-flow
- Commit
e6dc21f
- 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.