flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform
50
24%
Does it follow best practices?
Impact
100%
1.88xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/flow-nexus-swarm/SKILL.mdQuality
Discovery
7%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 this skill performs or when to select it. The only redeeming quality is the named platform 'Flow Nexus' which provides minimal distinctiveness.
Suggestions
Replace abstract buzzwords with specific concrete actions (e.g., 'Deploys AI agent swarms to cloud infrastructure, configures event triggers, monitors workflow pipelines on the Flow Nexus platform').
Add an explicit 'Use when...' clause with natural trigger terms users would actually say (e.g., 'Use when the user asks about deploying agents, setting up automated workflows, or configuring Flow Nexus pipelines').
Include natural keyword variations that users might use, such as 'deploy', 'automate', 'workflow', 'pipeline', 'Flow Nexus', 'swarm agents', to improve trigger term coverage.
| 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 a user would perform. No specific operations like 'deploy', 'configure', 'monitor' are enumerated. | 1 / 3 |
Completeness | The description vaguely hints at 'what' through buzzwords but provides no explicit 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent trigger guidance, and the 'what' itself 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, natural keywords a user would type when seeking this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Flow Nexus platform' provides some distinctiveness as a named platform, which reduces conflict risk somewhat. However, the generic terms 'cloud-based', 'AI', and 'workflow automation' could overlap with many other skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable MCP tool call examples with concrete parameters, which is its primary strength. However, it is severely bloated - repeating similar API calls across multiple sections, explaining concepts Claude already understands, and including filler sections like 'Common Use Cases' that add no actionable value. The content would be far more effective at 1/3 its current length with detailed patterns split into separate reference files.
Suggestions
Reduce content by 60-70%: eliminate the 'Common Use Cases' section entirely, consolidate redundant API call examples, and remove explanations of well-known concepts (CI/CD, ETL, topologies).
Split detailed patterns (Full-Stack Development, Research & Analysis, CI/CD Pipeline, Data Processing) into a separate PATTERNS.md file, keeping only one concise example inline.
Add explicit validation checkpoints to workflows: after workflow_execute, show checking workflow_status and handling failure states before proceeding.
Move the template catalog and best practices into separate referenced files (TEMPLATES.md, BEST_PRACTICES.md) to improve progressive disclosure.
| 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 'Common Use Cases' section is pure filler with no actionable content. Best Practices section repeats earlier content. | 1 / 3 |
Actionability | Provides concrete, executable MCP tool calls with specific parameter values and options. Every API function is shown with real arguments, valid syntax, and clear parameter documentation. The code examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Multi-step patterns (Full-Stack Development, CI/CD Pipeline) show clear sequencing with dependency chains, but there are no explicit validation checkpoints or error recovery feedback loops. The workflow patterns show steps but never verify success before proceeding - no 'check status before continuing' or 'if step fails, do X' guidance. | 2 / 3 |
Progressive Disclosure | Monolithic wall of content with everything inline. Despite having a table of contents, all content is in a single massive file with no references to external files for detailed API references, template catalogs, or pattern libraries. The sheer volume of inline content (patterns, templates, best practices, use cases) makes this difficult to navigate and would benefit enormously from splitting into separate files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%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
01070ed
- 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.