Name: agent-workflow-automation
Rating: 34.2 (1 reviews)
Author: ruvnet

Blog Docs Log in Get started

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

Content

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, poorly organized document that presents fictional/aspirational tooling as actionable guidance. The code examples reference non-existent packages and use incorrect MCP tool invocation syntax, making nothing executable. The content reads more like a marketing document for a hypothetical product than an actionable skill for Claude, with massive redundancy across sections that could be consolidated dramatically.

Suggestions

Replace fictional tool references (npx ruv-swarm, ruvnet/swarm-action) with actual executable commands using the MCP tools listed in the frontmatter, with correct invocation syntax

Reduce content to under 100 lines by eliminating redundant sections (e.g., consolidate the 10+ CLI command examples into a single reference table) and removing aspirational features

Add a clear sequential workflow (e.g., 1. Analyze repo → 2. Generate workflow → 3. Validate → 4. Deploy) with explicit validation checkpoints and error recovery

Split detailed templates and examples into separate bundle files (e.g., templates.md, security-workflows.md) and keep SKILL.md as a concise overview with clear navigation links

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 400+ lines with massive amounts of repetitive content. Many sections show slight variations of the same pattern (CLI commands with different flags). Explains concepts Claude already knows, and includes speculative/aspirational features (e.g., 'ruv-swarm' commands that appear to be fictional). The content could be reduced by 70%+ without losing actionable information.	1 / 3
Actionability	Despite containing many code blocks, nearly all examples reference a non-standard tool ('npx ruv-swarm actions') and fictional GitHub Actions ('ruvnet/swarm-action@v1') that don't appear to be real, executable tools. The MCP tool invocations use incorrect syntax (JSON-like objects instead of proper function calls). Nothing is copy-paste ready or verifiably executable.	1 / 3
Workflow Clarity	No clear sequential workflow with validation checkpoints exists. The content is a sprawling collection of disconnected code snippets and templates without a coherent process flow. There are no feedback loops, error recovery steps, or verification checkpoints despite dealing with CI/CD pipelines (destructive/batch operations). The user has no idea where to start or what order to follow.	1 / 3
Progressive Disclosure	Monolithic wall of text with 400+ lines of inline content that should be split across multiple files. References to external files (swarm-pr.md, swarm-issue.md, sync-coordinator.md) appear only at the very end with no context. No bundle files are provided to support these references. The document has many sections but no clear hierarchy or navigation strategy.	1 / 3
	Total	4 / 12 Passed

Description

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 meaningful information about what the skill does, when to use it, or how it differs from other skills. It fails on all dimensions due to complete lack of specificity, trigger terms, completeness, and distinctiveness.

Suggestions

Replace the generic label with specific concrete actions the skill performs, e.g., 'Creates automated pipelines, schedules recurring tasks, and chains tool invocations for multi-step processes.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to automate tasks, build workflows, set up pipelines, or chain multiple steps together.'

Specify the domain or platform to improve distinctiveness, e.g., 'Automates CI/CD pipelines in GitHub Actions' or 'Orchestrates multi-step data processing workflows.'

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Workflow-automation' is abstract and vague — it doesn't describe what the skill actually does (e.g., create workflows, schedule tasks, trigger actions).	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an 'agent skill' and how to invoke it, providing no functional or contextual information.	1 / 3
Trigger Term Quality	The only keyword is 'workflow-automation', which is a hyphenated compound unlikely to match natural user language. No natural terms like 'automate', 'pipeline', 'schedule', 'trigger', or specific workflow types are mentioned.	1 / 3
Distinctiveness Conflict Risk	'Workflow-automation' is extremely broad and could overlap with virtually any automation-related skill. There are no distinguishing details about what kind of workflows, what platform, or what domain.	1 / 3
	Total	4 / 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: 28c81c0

Reviewed: about 19 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.