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 managing release pipelines').
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 aspirational document that catalogs many possible release automation features without providing genuinely executable guidance. The heavy reliance on `npx ruv-swarm` commands with undocumented flags makes most content non-actionable, and the 400+ line monolithic structure violates both conciseness and progressive disclosure principles. The gh CLI snippets show some promise but are buried in fictional tooling.
Suggestions
Reduce content by 70%+: keep only the core release workflow (plan → version → build → test → deploy) with one concrete example each, moving integration examples and advanced features to separate referenced files.
Replace or document the `npx ruv-swarm` commands — either provide installation/setup instructions and verify the CLI flags exist, or replace with standard tooling (gh CLI, npm scripts, shell commands) that are actually executable.
Add explicit validation checkpoints and error recovery loops to the main release workflow (e.g., 'If build fails → check logs → fix → rebuild before proceeding to deploy').
Split into SKILL.md (overview + quick start + core workflow) with references to separate files for configuration, agents, integration examples, and emergency procedures.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with massive repetition. Many sections show slight variations of the same `npx ruv-swarm github` commands with different flags. The release notes template, best practices bullet lists, and multiple integration examples are padding that Claude doesn't need. The content could be reduced by 70%+ without losing actionable information. | 1 / 3 |
Actionability | Nearly all commands reference `npx ruv-swarm` which is an unverified/non-standard tool with no installation instructions or documentation links. The commands appear aspirational rather than executable — there's no way to verify these CLI flags actually work. The gh CLI portions are more concrete but are mixed with fictional tooling, making the whole skill unreliable. | 1 / 3 |
Workflow Clarity | The GitHub Actions workflow and the Release Orchestration section do show a sequential flow with some validation steps (draft → validate → publish). However, there are no explicit validation checkpoints or error recovery loops in most workflows. The relationship between the many 'agents' (changelog, version, build, test, deploy) and when/how they coordinate is unclear. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with everything inlined. The YAML config, workflow files, release notes templates, multiple agent definitions, integration examples, and emergency procedures are all dumped into one massive file. References to external files (workflow-automation.md, multi-repo-swarm.md) appear only at the very end with no clear navigation structure throughout. | 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
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.