flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill flow-nexus-swarm57
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.88xAgent success when using this skill
Validation for skill structure
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 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 comprehensive code examples covering multiple use cases. However, it suffers from verbosity with excessive explanatory text that Claude doesn't need, and the monolithic structure would benefit from splitting into separate reference files. Workflow examples lack explicit validation checkpoints despite involving complex multi-agent operations.
Suggestions
Remove explanatory text for concepts Claude already knows (e.g., 'Hierarchical: Tree structure with coordinator nodes' - just show when to use each topology)
Add explicit validation steps to workflow examples, such as checking swarm_status after init and verifying agent spawn success before orchestrating tasks
Split into separate files: move Templates & Patterns to TEMPLATES.md, API reference details to REFERENCE.md, and keep SKILL.md as a concise overview with links
Add error recovery feedback loops to workflow examples (e.g., 'If workflow_status shows failed: check audit_trail, fix issue, re-execute')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is comprehensive but overly verbose with extensive explanations of concepts (topology types, strategy guides, agent types) that Claude could infer. Many sections could be condensed significantly while preserving actionability. | 2 / 3 |
Actionability | Excellent executable code examples throughout with specific function calls, parameters, and options clearly documented. All examples are copy-paste ready with concrete parameter values and realistic use cases. | 3 / 3 |
Workflow Clarity | Multi-step workflows are well-sequenced with dependency management shown, but lacks explicit validation checkpoints and error recovery feedback loops. The 'Best Practices' section mentions error handling but doesn't integrate validation steps into the workflow examples themselves. | 2 / 3 |
Progressive Disclosure | Has a clear table of contents and organized sections, but the document is monolithic (~500+ lines) with content that could be split into separate reference files (templates, patterns, API reference). External links exist but point to external resources rather than companion skill files. | 2 / 3 |
Total | 9 / 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 | |
- 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.