agent-workflow-automation

Agent skill for workflow-automation - invoke with $agent-workflow-automation

6.33x

Quality

Does it follow best practices?

Impact

95%

6.33x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-workflow-automation/SKILL.md

Quality

Discovery

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 with no meaningful content. It fails on every dimension: it provides no concrete actions, no natural trigger terms, no explicit guidance on when to use it, and nothing to distinguish it from other skills. It would be nearly impossible for Claude to correctly select this skill from a pool of available options.

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 conditional logic between steps.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to automate a sequence of tasks, create a pipeline, set up triggers, or orchestrate multi-step processes.'

Include domain-specific keywords and file types or tools involved (e.g., 'cron jobs', 'CI/CD pipelines', 'task scheduling', 'event-driven automation') to improve distinctiveness and trigger term coverage.

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 vague label 'workflow-automation.'	1 / 3
Trigger Term Quality	The only keyword is 'workflow-automation,' which is generic jargon. There are no natural terms a user would say when needing this skill, and no variations or concrete trigger phrases.	1 / 3
Distinctiveness Conflict Risk	'Workflow-automation' is extremely generic and could overlap with virtually any skill that automates tasks, processes, or pipelines. There is nothing to distinguish it from other skills.	1 / 3
	Total	4 / 12 Passed

Implementation

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 references fictional tooling (ruv-swarm, swarm-action) without any setup or installation context. The examples are aspirational rather than executable, and the MCP tool invocations use incorrect syntax. The document would need to be fundamentally rewritten to provide real, actionable CI/CD workflow automation guidance with proper validation steps and realistic tooling.

Suggestions

Replace all fictional ruv-swarm/swarm-action references with real, executable tools and commands that Claude can actually use (e.g., actual GitHub Actions syntax, real gh CLI commands, actual MCP tool invocations with correct syntax)

Reduce content by 70%+ by removing repetitive examples and keeping only 2-3 core workflow patterns with complete, executable code

Add explicit validation checkpoints and error recovery steps to all multi-step workflows, especially deployment and security scanning pipelines

Move detailed examples into separate referenced files and keep SKILL.md as a concise overview with quick-start guidance and clear navigation to advanced topics

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 400+ lines with massive amounts of repetitive examples. Many sections show slight variations of the same pattern (npx ruv-swarm actions <command> with flags). The content explains concepts Claude already knows and includes speculative/aspirational tooling (ruv-swarm) with no indication these are real, executable tools. The document could be reduced by 70%+ without losing actionable information.	1 / 3
Actionability	Nearly all code examples reference a non-standard, likely fictional tool (npx ruv-swarm) and fictional GitHub Actions (ruvnet/swarm-action@v1) with no installation or setup instructions. The MCP tool invocations use invalid syntax (JSON-like objects as arguments). None of the code is copy-paste executable in any real environment. The skill describes rather than instructs.	1 / 3
Workflow Clarity	Despite showing many multi-step workflows, there are no validation checkpoints, no error recovery feedback loops, and no verification steps. The 'Self-Healing CI/CD' and deployment workflows lack any concrete validation. Steps are loosely described without clear sequencing or conditions for proceeding. Destructive operations like deployment have no rollback verification.	1 / 3
Progressive Disclosure	The document has section headers and references three related files at the bottom (swarm-pr.md, swarm-issue.md, sync-coordinator.md), showing some awareness of content splitting. However, the massive inline content (400+ lines of examples) should be split into separate reference files. The document is essentially a monolithic wall of examples with headers.	2 / 3
	Total	5 / 12 Passed

Validation

90%

Warnings & errors only

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: 619b263

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.