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 placeholder that restates the skill name without providing any meaningful information. It lacks concrete actions, trigger terms, explicit usage guidance, and any distinguishing detail. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.
Suggestions
Describe specific concrete actions the skill performs, e.g., 'Creates, schedules, and manages automated workflows including data pipelines, file processing routines, and notification triggers.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about automating tasks, scheduling jobs, building pipelines, or setting up recurring processes.'
Differentiate from related skills by specifying the exact domain or tooling, e.g., mentioning specific platforms, file types, or workflow patterns this skill handles.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Workflow-automation' is abstract and vague—it doesn't describe what specific tasks or operations the skill performs. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause and no description of capabilities beyond the skill name itself. | 1 / 3 |
Trigger Term Quality | The only keyword is 'workflow-automation,' which is generic jargon. There are no natural terms a user would say, such as specific workflow types, automation targets, or task names. | 1 / 3 |
Distinctiveness Conflict Risk | 'Workflow-automation' is extremely generic and could overlap with virtually any automation, scripting, CI/CD, or task-orchestration skill. There is nothing to distinguish 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 collection of fictional/aspirational code examples that reference non-existent tools and APIs. None of the provided code is executable, and the content reads more like a marketing document for a hypothetical 'ruv-swarm' product than actionable instructions for Claude. The skill fundamentally fails to provide concrete, real-world guidance for workflow automation.
Suggestions
Replace all fictional 'ruv-swarm' and made-up MCP tool references with actual executable commands using real GitHub Actions syntax, gh CLI, and the actual MCP tools listed in the frontmatter.
Reduce content by 70%+ by removing redundant sections (e.g., consolidate the 10+ variations of 'npx ruv-swarm actions <command>' into a focused set of real workflows).
Add a clear step-by-step workflow with validation checkpoints, e.g.: 1) Analyze repo structure, 2) Generate workflow YAML, 3) Validate syntax, 4) Create PR with workflow, 5) Verify workflow runs.
Move detailed examples (security scanning, release automation, documentation updates) into separate referenced files and keep SKILL.md as a concise overview with one or two core executable examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with massive amounts of repetitive content. Many sections show variations of the same pattern (spawn agents, run npx commands). Explains concepts Claude already knows, and includes speculative/aspirational features (predictive failures, self-healing CI) with no real executable substance. The content could be reduced by 70%+ without losing actionable information. | 1 / 3 |
Actionability | Nearly all code examples reference a fictional tool 'ruv-swarm' and fictional MCP tool invocations with made-up syntax (e.g., mcp__claude-flow__swarm_init with JSON-like inline objects). None of the code is executable or copy-paste ready. The YAML workflows reference non-existent GitHub Actions (ruvnet/swarm-action@v1). The JavaScript examples use fictional APIs and wouldn't run. | 1 / 3 |
Workflow Clarity | Despite describing CI/CD pipelines, there are no clear step-by-step workflows with validation checkpoints. The content presents disconnected code snippets without sequencing them into coherent processes. No verification steps, no error recovery loops, and no guidance on what to do when things fail. The 'Self-Healing Pipeline' section ironically has no actual healing logic. | 1 / 3 |
Progressive Disclosure | The content has section headers providing some structure, and references three related files at the bottom (swarm-pr.md, swarm-issue.md, sync-coordinator.md). However, the massive amount of inline content should be split into separate reference files. The monolithic structure with 15+ sections makes navigation difficult. | 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/ruflo
- Commit
0f7c750
- 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.