flow-nexus-neural

Train and deploy neural networks in distributed E2B sandboxes with Flow Nexus

2.07x

Quality

37%

Does it follow best practices?

Impact

79%

2.07x

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-neural/SKILL.md

Quality

Discovery

32%

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 too terse and lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others. While it names a specific domain (neural networks in E2B sandboxes with Flow Nexus), it doesn't enumerate concrete capabilities or provide natural trigger terms that users would commonly use.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user wants to train, fine-tune, or deploy machine learning models in sandboxed environments, or mentions E2B, Flow Nexus, or distributed training.'

Include more natural trigger terms users would say, such as 'deep learning', 'model training', 'ML deployment', 'machine learning', 'GPU training', 'distributed computing'.

Expand the capability list with specific actions, e.g., 'Configures distributed training jobs, manages sandbox environments, monitors training progress, deploys trained models to endpoints.'

Dimension	Reasoning	Score
Specificity	Names the domain (neural networks, distributed sandboxes) and two actions (train and deploy), but lacks comprehensive detail about specific capabilities beyond those two high-level actions.	2 / 3
Completeness	Describes what it does (train and deploy neural networks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also thin, so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'neural networks', 'train', 'deploy', and 'distributed', but 'E2B sandboxes' and 'Flow Nexus' are product-specific jargon that users may not naturally use. Missing common variations like 'deep learning', 'model training', 'ML', 'machine learning'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'E2B sandboxes' and 'Flow Nexus' adds some distinctiveness, but 'train and deploy neural networks' is broad enough to overlap with other ML/AI-related skills. The product-specific terms help somewhat but aren't sufficient for clear disambiguation.	2 / 3
	Total	7 / 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 is highly actionable with concrete, executable MCP tool calls and realistic response examples, which is its primary strength. However, it is extremely verbose and repetitive — architecture examples appear multiple times, common use cases duplicate earlier content, and the entire document could be cut by 60%+ without losing information. The lack of progressive disclosure (everything crammed into one file) and missing validation checkpoints in multi-step workflows are significant weaknesses.

Suggestions

Split content into separate files: move Architecture Patterns to ARCHITECTURES.md, Common Use Cases to EXAMPLES.md, and Distributed Training details to DISTRIBUTED.md, keeping only a concise overview with links in SKILL.md.

Remove duplicate content — the Architecture Patterns section repeats what's already shown in the training examples above; choose one location for each example.

Add explicit validation checkpoints to the distributed training workflow (e.g., verify cluster status is 'ready' before deploying nodes, confirm all nodes are 'active' before starting training).

Remove obvious best practices that Claude already knows (e.g., 'Start Small', 'Monitor Training') and trim response JSON examples to only show fields that are non-obvious or needed for subsequent steps.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~500+ lines. Massive amounts of repetition — architecture patterns are shown in full examples AND repeated in the 'Architecture Patterns' section. Common use cases duplicate earlier examples. Response JSON examples add bulk without teaching Claude anything new. The 'Best Practices' section states obvious advice like 'Start Small' and 'Monitor Training'.	1 / 3
Actionability	Every capability includes concrete, executable MCP tool calls with full parameter objects and expected response JSON. The examples are copy-paste ready with realistic configurations, and cover the full lifecycle from training to inference to cluster management.	3 / 3
Workflow Clarity	The distributed training section shows a reasonable sequence (init cluster → deploy nodes → connect → train → monitor → terminate), but there are no explicit validation checkpoints or error-recovery feedback loops between steps. The 'Common Use Cases' section shows sequential workflows but lacks verification steps (e.g., checking cluster is ready before training, validating model before inference). The troubleshooting section is separate rather than integrated into workflows.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with everything inline. The architecture patterns, common use cases, and detailed examples could all be split into separate referenced files. The 'Related Skills' and 'Resources' sections at the bottom hint at external references but the body itself contains far too much detail for a single SKILL.md overview.	1 / 3
	Total	7 / 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 (739 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: 3 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.