agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm

2.94x

Quality

13%

Does it follow best practices?

Impact

100%

2.94x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Discovery

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 only a name and invocation command without explaining what the skill does, what actions it performs, or when it should be used. Claude would have no basis for selecting this skill appropriately from a list of available skills.

Suggestions

Add concrete actions describing what release-swarm does (e.g., 'Coordinates multi-agent release workflows, manages version bumps, generates changelogs, and orchestrates deployment pipelines').

Include an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user mentions releases, deployments, version management, changelogs, or coordinating release processes').

Remove or supplement the invocation syntax with functional description - the command syntax alone provides no selection guidance for Claude.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for release-swarm' is completely abstract with no indication of what the skill actually does.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command with no functional description or usage guidance.	1 / 3
Trigger Term Quality	The only potential trigger term is 'release-swarm' which is technical jargon, not a natural keyword users would say. No common variations or natural language terms are provided.	1 / 3
Distinctiveness Conflict Risk	While 'release-swarm' is a unique term, the description is so vague that Claude cannot determine when to use it versus any other skill. The lack of context makes proper skill selection impossible.	1 / 3
	Total	4 / 12 Passed

Implementation

27%

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

This skill suffers from severe verbosity and poor organization, presenting a massive amount of content that overwhelms rather than guides. While it contains some actionable gh CLI examples, much of the content relies on fictional 'ruv-swarm' commands and could be dramatically condensed. The lack of progressive disclosure means Claude must process 500+ lines when a concise overview with references would be far more effective.

Suggestions

Reduce content by 80% - keep only a quick start section with 2-3 core workflows, move all configuration examples and advanced features to separate reference files

Clarify which commands are real (gh CLI) vs fictional (npx ruv-swarm) or remove fictional tooling entirely

Add explicit validation checkpoints with error handling: 'If X fails, do Y before proceeding'

Create a clear hierarchy: SKILL.md as overview (<100 lines) pointing to RELEASE-CONFIG.md, DEPLOYMENT.md, EMERGENCY.md for detailed procedures

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 500+ lines with massive redundancy. Multiple sections repeat similar concepts (release planning, orchestration, deployment). Contains extensive YAML configs and bash examples that could be consolidated or referenced externally.	1 / 3
Actionability	Provides concrete bash commands and YAML configs, but relies heavily on fictional 'npx ruv-swarm' commands that aren't real executables. The gh CLI examples are actionable, but mixed with non-existent tooling creates confusion about what's actually executable.	2 / 3
Workflow Clarity	Steps are listed in various sections but validation checkpoints are inconsistent. The 'Standard Release Flow' has some sequence but lacks explicit error recovery steps. Progressive deployment section mentions validation but doesn't show how to handle failures.	2 / 3
Progressive Disclosure	Monolithic wall of content with everything inline. References to external files at the end (workflow-automation.md, multi-repo-swarm.md) but the main content dumps hundreds of lines of configs, examples, and procedures that should be split into separate reference files.	1 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 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/claude-flow
Commit: b2618f9

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.