agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm
39
6%
Does it follow best practices?
Impact
100%
2.94xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-release-swarm/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 essentially non-functional as a skill selector. It provides only an invocation command and a label ('release-swarm') with zero information about capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a pool of available skills.
Suggestions
Describe what the skill actually does with concrete actions (e.g., 'Coordinates multi-agent release workflows, manages version bumping, changelog generation, and deployment orchestration').
Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks about releasing software, cutting a release, deploying versions, or coordinating release processes').
Remove the invocation syntax ('invoke with $agent-release-swarm') from the description and replace it with functional information that helps Claude decide when to use this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for release-swarm' is entirely vague and does not describe what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states the invocation command, providing no functional or contextual information. | 1 / 3 |
Trigger Term Quality | The only keyword is 'release-swarm', which is a technical/internal term unlikely to be naturally used by users. There are no natural language trigger terms describing the task domain. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it provides no distinguishing characteristics. Without knowing what 'release-swarm' does, it could conflict with any release-related or agent-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
12%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 reads more like marketing material for a hypothetical `ruv-swarm` tool than a practical skill for Claude. The vast majority of commands are not executable since they depend on an unverifiable CLI tool, and the content is heavily padded with repetitive patterns, unnecessary templates, and best-practice lists that Claude already knows. The sheer length (~500 lines) with minimal unique, actionable content makes this a poor use of context window.
Suggestions
Replace speculative `npx ruv-swarm` commands with actual executable code using real tools (gh CLI, npm, docker) that Claude can run directly, or clearly document how to install and verify the ruv-swarm tool.
Reduce content by 70-80% - eliminate redundant integration examples (NPM, Docker, Mobile all follow the same pattern), remove the release notes template, and cut the best practices section entirely.
Split detailed configuration (release config YAML, GitHub Actions workflow) into separate referenced files and keep SKILL.md as a concise overview with quick-start instructions.
Add explicit validation checkpoints with error recovery steps (e.g., 'If build fails, check X; if version conflict, do Y') instead of just listing `--block-on-failure` flags.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with massive amounts of repetitive CLI examples that are essentially variations of the same pattern (`npx ruv-swarm github <subcommand> --flags`). Includes unnecessary sections like release notes templates, best practices lists Claude already knows, and redundant integration examples that add little unique value. | 1 / 3 |
Actionability | Nearly all commands reference `npx ruv-swarm` which is an unverifiable, likely non-existent tool - none of these commands are executable or copy-paste ready. The `gh` CLI examples are more concrete but are embedded in speculative pipelines with shell variable interpolation that wouldn't work as-is. The skill describes capabilities rather than providing genuinely actionable instructions. | 1 / 3 |
Workflow Clarity | The Standard Release Flow section provides a reasonable sequential workflow with steps, and there's some notion of validation (pre-release checks, compatibility testing). However, there are no explicit feedback loops for error recovery, and the validation steps are just more `npx ruv-swarm` commands with `--block-on-failure` flags rather than concrete checkpoint logic. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no meaningful content separation. References to `workflow-automation.md` and `multi-repo-swarm.md` at the bottom, but no bundle files are provided. The entire document dumps everything inline - configuration examples, agent descriptions, workflow YAML, templates, best practices - with no layered structure. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%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 (588 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- ruvnet/ruflo
- Commit
619b263
- 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.