agent-workflow
Agent skill for workflow - invoke with $agent-workflow
39
7%
Does it follow best practices?
Impact
95%
2.43xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-workflow/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 critically deficient across all dimensions. It provides no information about what the skill does, when it should be used, or what distinguishes it from other skills. It reads more like a label than a functional description, making it essentially useless for skill selection among multiple options.
Suggestions
Replace the entire description with concrete actions the skill performs, e.g., 'Orchestrates multi-step task pipelines, manages sequential agent handoffs, and tracks workflow state' or whatever the skill actually does.
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to automate a sequence of tasks, create a pipeline, or coordinate multiple steps in a process.'
Remove the invocation instruction ('invoke with $agent-workflow') from the description—this is metadata, not a capability description—and replace it with domain-specific keywords that distinguish this skill from others.
| 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, no description of capabilities, and no explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only potentially relevant term is 'workflow', which is extremely generic. There are no natural keywords a user would say when needing this 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 task-oriented skill. There is nothing distinctive about this description that would help Claude differentiate it from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
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 persona description and feature advertisement than actionable operational guidance. It is heavily padded with abstract concepts, vague quality standards, and pattern lists that Claude already understands, while lacking concrete workflows with validation steps, expected outputs, and error recovery procedures. The MCP tool examples are the only useful part but are incomplete and lack context on when/how to use them in sequence.
Suggestions
Remove the verbose persona description, quality standards, and pattern lists—replace with a concise quick-start showing a complete workflow creation → execution → monitoring sequence with expected outputs at each step.
Add explicit validation checkpoints and error recovery steps (e.g., what to do when workflow_status returns a failed step, how to retry or rollback).
Document the MCP tool parameters more precisely—show required vs optional fields, expected return values, and edge cases rather than single illustrative examples.
Split advanced features (vector-based agent matching, cross-workflow orchestration) into a separate reference file and keep SKILL.md focused on the core create/execute/monitor workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of concepts Claude already knows (error handling, scalability, fault tolerance). The 'quality standards', 'advanced features', and 'workflow patterns' sections are padded descriptions that don't add actionable value. Much of the content reads like a marketing brochure rather than operational instructions. | 1 / 3 |
Actionability | The JavaScript code examples showing MCP tool calls are concrete and somewhat useful, but they are incomplete—no expected outputs are shown, parameter options aren't documented, and the examples are illustrative rather than copy-paste ready for real scenarios. The workflow design approach is a vague numbered list without executable guidance. | 2 / 3 |
Workflow Clarity | The six-step 'workflow design approach' is abstract and lacks validation checkpoints. There's no guidance on what to do when workflow execution fails, no feedback loops for error recovery, and no concrete sequence for multi-step operations like creating then executing then monitoring a workflow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files, no clear navigation structure, and no separation between quick-start essentials and advanced reference material. Everything is dumped into a single flat document with bullet-heavy sections. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
100%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
398f7c2
- 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.