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 is an extremely weak description that provides almost no useful information for skill selection. It lacks any concrete actions, trigger terms, use-case guidance, or distinguishing characteristics. It reads more like a label than a description and would be nearly impossible for Claude to correctly select from a pool of available skills.
Suggestions
Describe the specific actions this skill performs (e.g., 'Creates, manages, and automates multi-step workflows including task sequencing, dependency tracking, and status monitoring').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to automate a process, create a pipeline, orchestrate tasks, or manage sequential steps').
Clarify the specific domain or type of workflow to distinguish this skill from other potentially overlapping skills (e.g., CI/CD workflows, data processing pipelines, approval workflows).
| 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 | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance. | 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. 'Agent' and '$agent-workflow' are technical invocation terms, not user-facing trigger terms. | 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 marketing description or role-play prompt than actionable technical guidance. It is padded with generic responsibilities, quality standards, and feature lists that Claude already understands, while lacking concrete workflows, validation steps, and executable examples. The MCP tool call examples are the only useful part but are insufficient without proper workflow sequencing and error handling guidance.
Suggestions
Remove the generic 'core responsibilities', 'quality standards', and 'advanced features' bullet lists — these describe what Claude should already know and waste tokens without adding value.
Add a concrete end-to-end workflow example showing the exact sequence of MCP calls (create → execute → monitor → handle errors) with explicit validation checkpoints between steps.
Include error handling examples showing what to do when workflow_status returns failures, with specific retry/rollback MCP calls.
Split advanced patterns (CI/CD, ETL, conditional workflows) into a separate reference file and keep SKILL.md as a concise quick-start guide.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of responsibilities, patterns, quality standards, and advanced features that Claude already knows or could infer. The 'Your core responsibilities' and 'Quality standards' sections are generic platitudes that waste tokens without adding actionable value. | 1 / 3 |
Actionability | The JavaScript code examples showing MCP tool calls are concrete and somewhat useful, but they are illustrative rather than executable in a real context. The workflow design approach is a generic numbered list without specific commands or concrete guidance for actual implementation. | 2 / 3 |
Workflow Clarity | The 'workflow design approach' is a vague 6-step list with no validation checkpoints, no error recovery steps, and no feedback loops. For a skill that involves orchestrating complex multi-step workflows, there is no clear sequence showing how to validate workflow creation, handle execution failures, or verify successful completion. | 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 content and advanced features. Everything is dumped into a single flat document with bullet-point lists. | 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
0f7c750
- 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.