flow-nexus-swarm

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

1.88x

Quality

17%

Does it follow best practices?

Impact

100%

1.88x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/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 jargon without conveying concrete actions or clear trigger conditions. It fails to tell Claude what specific tasks the skill performs or when it should be selected. The only slightly redeeming quality is the mention of a specific platform name ('Flow Nexus'), which provides minimal distinctiveness.

Suggestions

Replace abstract buzzwords with concrete actions the skill performs (e.g., 'Deploys AI agent swarms to cloud infrastructure, configures event triggers, monitors workflow execution on the Flow Nexus platform').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about deploying agents to Flow Nexus, setting up automated workflows, or managing cloud swarm configurations').

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

Dimension	Reasoning	Score
Specificity	The description uses buzzword-heavy, abstract language ('cloud-based AI swarm deployment', 'event-driven workflow automation') without listing any concrete actions the skill performs. There are no specific verbs describing what the skill actually does.	1 / 3
Completeness	The description vaguely hints at 'what' through buzzwords but provides no concrete capabilities, and there is no 'when' clause or explicit trigger guidance whatsoever. Both dimensions are very weak.	1 / 3
Trigger Term Quality	The terms used are highly technical jargon ('AI swarm deployment', 'event-driven workflow automation', 'Flow Nexus platform') that users would rarely naturally say. There are no common, natural keywords a user would use when needing this skill.	1 / 3
Distinctiveness Conflict Risk	The mention of 'Flow Nexus platform' provides some specificity that could distinguish it from other skills, but the broader terms like 'workflow automation' and 'cloud-based' are generic 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 a comprehensive but excessively verbose reference document that tries to cover every aspect of the Flow Nexus platform in a single file. While it provides useful MCP tool call syntax, it suffers from significant redundancy (topology explanations repeated, similar patterns shown multiple times), lacks validation/error recovery workflows critical for cloud operations, and fails to leverage progressive disclosure despite its length. The content would benefit greatly from aggressive trimming and splitting into focused reference files.

Suggestions

Reduce content by 60-70%: remove redundant topology/strategy explanations, consolidate the 4+ workflow patterns into one annotated example with a reference to a PATTERNS.md file for additional templates, and eliminate the 'Common Use Cases' section which adds no actionable guidance.

Add explicit validation checkpoints to workflows: after swarm_init check status before spawning agents, after workflow_execute verify completion with workflow_status, and include a concrete error recovery loop (check status → diagnose → retry/rollback).

Split into multiple files: keep SKILL.md as a concise overview (~80 lines) with quick-start example, then reference separate files like PATTERNS.md (workflow templates), API-REFERENCE.md (all tool calls), and SETUP.md (authentication/installation).

Remove explanations of general concepts (what CI/CD is, what ETL means, what mesh topology is) and focus only on Flow Nexus-specific behavior and tool call parameters that Claude wouldn't already know.

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 redundancy: topology guide repeated in overview and best practices, multiple near-identical workflow patterns, and unnecessary lists of common use cases that add no actionable value. The 'Best Practices' section largely restates earlier content with minor variations.	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 pseudo-async patterns (await on MCP calls), reference workflow_ids that wouldn't exist yet, and the multi-swarm coordination example mixes JavaScript await syntax with MCP tool call conventions inconsistently. The tool calls themselves are well-structured but the surrounding orchestration logic is pseudocode.	2 / 3
Workflow Clarity	The Full-Stack Development Pattern shows a clear 4-step sequence (init → spawn → create workflow → execute), and workflow steps have dependency chains. However, there are no validation checkpoints or error recovery feedback loops anywhere. For cloud-based swarm operations that could fail, there's no guidance on checking if swarm_init succeeded before spawning agents, no verification after workflow execution, and the error handling best practice only shows metadata configuration rather than an actual validate-fix-retry workflow.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files despite the content being long enough to warrant splitting. The table of contents provides internal anchors but everything is inline. API reference details, template catalogs, and pattern examples could all be separate files. No bundle files exist to support any progressive disclosure structure.	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/claude-flow
Commit: 9d4a9ea

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