agent-workflow

Agent skill for workflow - invoke with $agent-workflow

2.43x

Quality

Does it follow best practices?

Impact

95%

2.43x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Content

14%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a marketing description or persona prompt than actionable technical guidance. It is heavily padded with abstract descriptions of capabilities, patterns, and quality standards that Claude already understands, while lacking concrete executable workflows, validation steps, error handling procedures, and structured progressive disclosure. The MCP tool call examples are the only somewhat useful content but remain incomplete.

Suggestions

Remove all persona framing and abstract capability descriptions; replace with a concise quick-start section showing a complete workflow creation-to-execution sequence with expected outputs.

Add explicit validation checkpoints and error recovery steps — e.g., what to check after workflow_execute, how to handle failed steps, and when to use workflow_status to verify completion.

Replace the abstract 'workflow design approach' list with concrete, sequenced instructions showing how to chain the MCP tool calls together for a real workflow scenario.

Extract the workflow patterns catalog into a separate reference file and keep SKILL.md focused on the essential how-to guidance.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations of concepts Claude already knows (what CI/CD is, what ETL pipelines are, what error handling means). The 'core responsibilities', 'workflow patterns', 'quality standards', and 'advanced features' sections are largely padded descriptions that don't add actionable value. The persona framing ('You are a Flow Nexus Workflow Agent') wastes tokens.	1 / 3
Actionability	The JavaScript code examples showing MCP tool calls are somewhat concrete and provide specific function signatures with parameters, but they are illustrative rather than executable — there's no guidance on what the actual return values look like, how to handle responses, or complete workflows connecting multiple calls. The workflow design approach is abstract (e.g., 'Understand the automation objectives').	2 / 3
Workflow Clarity	The 6-step 'workflow design approach' is abstract and describes a general methodology rather than concrete sequenced steps. There are no validation checkpoints, no error recovery procedures, no feedback loops, and no guidance on what to do when a workflow step fails. For a skill involving multi-step orchestration and potentially destructive operations, this is insufficient.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files, no clear separation between quick-start and advanced content, and no navigation structure. Everything is dumped into a single file with no bundle files to support it.	1 / 3
	Total	5 / 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 is an extremely weak description that provides essentially no useful information for skill selection. It fails on every dimension: it names no concrete actions, includes no natural trigger terms, answers neither 'what' nor 'when,' and is so generic it would conflict with many other skills. It reads more like a label than a description.

Suggestions

Replace the vague 'workflow' label with specific concrete actions the skill performs (e.g., 'Creates, manages, and automates multi-step workflows including task sequencing, conditional branching, and status tracking').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about automating tasks, creating pipelines, orchestrating steps, or managing sequential processes').

Remove the invocation instruction ('invoke with $agent-workflow') from the description and focus entirely on capability and trigger information that helps Claude select the right skill.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for workflow' is entirely vague—it doesn't describe what the skill does, what domain it operates in, or what actions it 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.	1 / 3
Trigger Term Quality	The only potentially relevant term is 'workflow,' which is extremely generic and not a natural keyword a user would use to find a specific skill. 'invoke with $agent-workflow' is an invocation instruction, not a trigger term.	1 / 3
Distinctiveness Conflict Risk	'Workflow' is an extremely broad term that could overlap with virtually any process-oriented skill. There is nothing distinctive about this description to differentiate it from other skills.	1 / 3
	Total	4 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Commit: cc8830d

Reviewed: 4 days 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.