flow-nexus-swarm

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

2.07x

Quality

36%

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 relies heavily on marketing buzzwords and technical jargon without explaining what Claude can actually do or when to use this skill. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly impossible for Claude to correctly select this skill from a pool of options.

Suggestions

Replace abstract terms with specific actions (e.g., 'Deploy AI agents to Flow Nexus, configure event triggers, monitor swarm status, create automated workflows').

Add a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions Flow Nexus, swarm deployment, or needs to set up automated cloud workflows').

Include concrete file types, commands, or scenarios that would help distinguish this skill (e.g., 'workflow configuration files, .yaml pipelines, Flow Nexus API').

Dimension	Reasoning	Score
Specificity	The description uses vague, buzzword-heavy language like 'AI swarm deployment' and 'event-driven workflow automation' without listing any concrete actions Claude can perform. No specific operations are described.	1 / 3
Completeness	Only vaguely addresses 'what' with abstract concepts, and completely missing any 'when' guidance. No 'Use when...' clause or explicit trigger conditions are provided.	1 / 3
Trigger Term Quality	Contains technical jargon ('AI swarm', 'event-driven workflow automation', 'Flow Nexus') that users are unlikely to naturally say. Missing common user-facing terms that would trigger this skill.	1 / 3
Distinctiveness Conflict Risk	The mention of 'Flow Nexus platform' provides some specificity to a particular tool, but 'workflow automation' and 'cloud-based' are generic enough to potentially overlap with other automation or cloud skills.	2 / 3
	Total	5 / 12 Passed

Implementation

64%

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

This skill provides highly actionable, executable guidance for Flow Nexus swarm orchestration with excellent code examples and comprehensive coverage. However, it suffers from verbosity (explanatory text that Claude doesn't need), missing validation checkpoints in workflows, and a monolithic structure that would benefit from splitting into multiple reference files.

Suggestions

Remove explanatory prose like 'best for complex projects' and topology/strategy descriptions - present options as terse lists or tables instead

Add explicit validation steps to workflow patterns (e.g., 'Check swarm_status before proceeding to task_orchestrate', 'Verify workflow_status shows success before deploy_prod')

Split into multiple files: move Templates & Patterns to TEMPLATES.md, Advanced Features to ADVANCED.md, and Common Use Cases to EXAMPLES.md with clear links from the main skill

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some unnecessary explanatory text (e.g., explaining what each topology is 'best for', redundant descriptions). The content could be tightened significantly while preserving all actionable information.	2 / 3
Actionability	Excellent executable code examples throughout with specific MCP tool calls, complete parameter options, and copy-paste ready patterns. Every major feature has concrete, runnable JavaScript examples.	3 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with dependencies, but validation/verification checkpoints are largely missing. The patterns show execution but lack explicit 'validate before proceeding' steps or error recovery feedback loops.	2 / 3
Progressive Disclosure	Good table of contents and section organization, but the document is monolithic (~500 lines) with content that could be split into separate files (e.g., templates, patterns, advanced features). References to external docs exist but are minimal.	2 / 3
	Total	9 / 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: 8db2712

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