flow-nexus-swarm

Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform

2.07x

Quality

17%

Does it follow best practices?

Impact

87%

2.07x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/flow-nexus-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 heavily padded with buzzwords and technical jargon without providing concrete, actionable information about what the skill does or when it should be used. It reads more like marketing copy than a functional skill description. The lack of specific actions, natural trigger terms, and explicit usage guidance makes it very difficult for Claude to correctly select this skill.

Suggestions

Replace abstract buzzwords with concrete actions the skill performs, e.g., 'Deploys AI agent swarms to cloud infrastructure, configures event triggers, and manages automated workflows on the Flow Nexus platform.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about deploying agents to Flow Nexus, setting up event-driven pipelines, or managing swarm configurations.'

Include specific file types, commands, or platform features that would help distinguish this skill from generic cloud or automation skills.

Dimension	Reasoning	Score
Specificity	The description uses vague, buzzword-heavy language like 'cloud-based AI swarm deployment' and 'event-driven workflow automation' without listing any concrete actions the skill performs. No specific operations like 'deploy containers', 'configure triggers', or 'monitor workflows' are mentioned.	1 / 3
Completeness	The description vaguely hints at 'what' through abstract concepts but provides no explicit 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent trigger guidance, and even the 'what' is too abstract to be useful.	1 / 3
Trigger Term Quality	The terms used are highly technical jargon ('AI swarm deployment', 'event-driven workflow automation', 'Flow Nexus platform') that users are unlikely to naturally say. There are no common user-facing keywords or natural language variations included.	1 / 3
Distinctiveness Conflict Risk	The mention of 'Flow Nexus platform' provides some distinctiveness as a named platform, which reduces conflict risk somewhat. However, terms like 'cloud-based' and 'workflow automation' are broad enough to overlap with many other skills.	2 / 3
	Total	5 / 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 is excessively verbose, repeating similar API call patterns across numerous sections without adding proportional value. While it provides concrete MCP tool call syntax (a strength), it buries actionable content under layers of explanatory text about concepts Claude already understands. The lack of any bundle files means all content is monolithically packed into one document, and the absence of validation checkpoints in multi-step cloud orchestration workflows is a notable safety gap.

Suggestions

Reduce content by 60-70%: eliminate the topology/strategy/agent type explanation sections, the 'Common Use Cases' bullet lists, and redundant pattern examples. Keep one comprehensive pattern and reference others in separate files.

Split into multiple files: move Templates & Patterns, Advanced Features, and individual workflow patterns (CI/CD, ETL, Research) into separate referenced markdown files to enable progressive disclosure.

Add explicit validation checkpoints to workflows: after swarm_init check status before spawning agents, after agent_spawn verify agents are ready, after workflow_execute check workflow_status before proceeding.

Standardize code examples to use consistent MCP tool call syntax throughout—either use the `mcp__flow-nexus__tool_name({...})` format consistently or clarify when async/await patterns apply.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Extensively explains concepts Claude already knows (what topologies are, what ETL means, what CI/CD is). Massive amounts of redundant examples—the same API calls are shown multiple times with slight variations. The topology guide, strategy guide, agent types, and execution modes sections all explain obvious concepts. The 'Common Use Cases' section is pure filler with no actionable content.	1 / 3
Actionability	Provides concrete MCP tool call syntax with parameters and options, which is useful. However, many examples are not truly executable—they use pseudocode patterns like `const status = await mcp__flow-nexus__swarm_status()` mixing async/await with MCP tool call syntax inconsistently. The multi-swarm coordination section uses `await` syntax that doesn't match the MCP calling convention used elsewhere. Key details like error handling responses and expected output formats are missing.	2 / 3
Workflow Clarity	The Full-Stack Development Pattern shows a clear 4-step sequence (init → spawn → create workflow → execute), and workflow steps include dependency chains. However, there are no validation checkpoints—no guidance on checking if swarm initialization succeeded before spawning agents, no verification that agents spawned correctly before orchestrating tasks, and no error recovery feedback loops. For cloud-based orchestration involving potentially destructive or costly operations, this is a significant gap.	2 / 3
Progressive Disclosure	Monolithic wall of text with no bundle files to reference. Everything is crammed into a single massive document. The table of contents suggests structure but the content itself is not split across files. Content like the full CI/CD pipeline pattern, ETL pipeline pattern, and detailed template listings should be in separate reference files. No external references exist despite the document being far too long for a single SKILL.md.	1 / 3
	Total	6 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (611 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: ruvnet/agentic-flow
Commit: 6a06854

Reviewed: 9 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.