agent-workflow-automation
Agent skill for workflow-automation - invoke with $agent-workflow-automation
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-workflow-automation43
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/skillEvaluation — 95%
↑ 6.33xAgent success when using this skill
Validation 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 functions more as a label than a description, providing only a vague category name and invocation command. Claude would have no basis for selecting this skill appropriately since there's no information about what it does or when to use it.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Creates automated workflows, schedules recurring tasks, sets up conditional triggers between applications')
Include an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user wants to automate repetitive tasks, create scheduled jobs, or connect different tools together')
Specify the domain or types of workflows supported to distinguish from other automation-related skills (e.g., 'for CI/CD pipelines', 'for data processing', 'for notification systems')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for workflow-automation' is entirely abstract with no indication of what specific tasks it performs. | 1 / 3 |
Completeness | Missing both 'what' and 'when'. The description only states it's an agent skill and how to invoke it, but provides no information about capabilities or usage triggers. | 1 / 3 |
Trigger Term Quality | The only keyword is 'workflow-automation' which is technical jargon. No natural user terms like 'automate tasks', 'schedule', 'triggers', or specific workflow types are mentioned. | 1 / 3 |
Distinctiveness Conflict Risk | 'Workflow-automation' is extremely generic and could conflict with any skill involving automation, scheduling, task management, or process handling. No distinguishing characteristics provided. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill suffers from severe verbosity, presenting dozens of similar YAML workflow examples without clear organization or prioritization. While it contains concrete code examples, the reliance on undocumented fictional tools (ruv-swarm, mcp__claude-flow__*) undermines actionability. The document needs aggressive trimming and restructuring into a concise overview with references to detailed examples.
Suggestions
Reduce content by 75%: Keep one example per concept (e.g., one workflow template, one security scan, one deployment example) and move the rest to separate reference files
Add a Quick Start section (under 20 lines) at the top showing the minimal viable workflow automation setup
Document prerequisites: Explain what ruv-swarm and mcp__claude-flow__* tools are, how to install them, and verify they're working before proceeding
Restructure with clear progressive disclosure: Overview (20 lines) → Quick Start (30 lines) → References to TEMPLATES.md, ADVANCED.md, EXAMPLES.md for detailed content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with massive amounts of example YAML/code that could be condensed. Many sections repeat similar patterns (workflow templates, integration examples) without adding unique value. The document is over 400 lines when the core concepts could be conveyed in under 100. | 1 / 3 |
Actionability | Provides concrete YAML examples and bash commands that appear executable, but relies heavily on fictional tools (ruv-swarm, mcp__claude-flow__*) without explaining how to actually install or configure them. The examples look copy-paste ready but may not actually work without significant setup not documented here. | 2 / 3 |
Workflow Clarity | Individual workflow examples show clear sequences, but the overall document lacks a coherent workflow for how to actually use this skill. No validation checkpoints for the multi-step processes, and the relationship between different sections (Core Features, Advanced Workflows, Advanced Swarm Workflow Automation) is unclear. | 2 / 3 |
Progressive Disclosure | Monolithic wall of content with no clear hierarchy. Everything is dumped into one massive file with minimal organization. References to other files at the end (swarm-pr.md, swarm-issue.md) come after 400+ lines of content. No clear quick-start section that points to detailed references. | 1 / 3 |
Total | 6 / 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 | |
- 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.