flow-nexus-swarm

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

2.07x

Quality

61%

Does it follow best practices?

Impact

87%

2.07x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/flow-nexus-swarm/SKILL.md

Quality

Content

65%

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

The body is highly actionable with abundant executable examples and clear section structure, but it is verbose/repetitive for a single file and lacks explicit validation feedback loops for its destructive and batch operations. Splitting detailed catalogs into reference files and adding validation checkpoints would improve it.

Suggestions

Add explicit validation checkpoints and error-recovery feedback loops to batch/destructive workflows (e.g. verify swarm_status before swarm_destroy, validate workflow_status before promoting staging to prod).

Split the large template catalog and multi-pattern examples into separate reference files (e.g. TEMPLATES.md, PATTERNS.md) referenced one level deep from the overview.

Trim repetition between the 'Templates & Patterns', 'Agent Orchestration' patterns, and 'Best Practices' sections to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable code with little concept-explanation padding, but it is long and somewhat repetitive across the patterns, templates, and best-practices sections, fitting 'mostly efficient but could be tightened'.	2 / 3
Actionability	It provides extensive, concrete, copy-paste-ready JavaScript MCP calls with parameters and inline option comments, matching the 'fully executable code/commands; specific examples' anchor.	3 / 3
Workflow Clarity	Multi-step patterns are sequenced with numbered comments, but batch/destructive operations like swarm_destroy and production deployments lack explicit validation checkpoints or feedback loops, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	It is a single monolithic file with a TOC and well-organized sections but no bundle files or one-level-deep references, and substantial content (template catalog, patterns) that could be split out is inline.	2 / 3
	Total	9 / 12 Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is product-specific and reasonably distinct, but it reads as a single capability phrase without an explicit 'when to use' trigger clause or a list of concrete actions. Adding a 'Use when...' clause with natural user terms would lift completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases a user would say (e.g. 'Use when deploying AI agent swarms, building event-driven workflows, or processing message queues').

Expand the capability sentence into a short list of concrete actions (e.g. initialize swarms, spawn agents, orchestrate tasks, create event-driven workflows).

Include common variation terms users might say ('agent swarms', 'message queue processing', 'task orchestration') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('AI swarm deployment' and 'event-driven workflow automation') but is a single phrase rather than a list of multiple concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what the skill does but has no 'Use when...' or equivalent trigger clause for when to use it, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Relevant terms like 'AI swarm', 'workflow automation', and 'Flow Nexus' appear, but common natural variations a user would say are limited and no explicit trigger phrasing is given, matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	Tying the capability to the specific 'Flow Nexus platform' gives it a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: ruvnet/agentic-flow
Path: .claude/skills/flow-nexus-swarm/SKILL.md
Commit: d069fff

Reviewed: about 12 hours 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.