flow-nexus-neural

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

7.38x

Quality

37%

Does it follow best practices?

Impact

96%

7.38x

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-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. While it names a specific domain and two actions, it relies on product-specific jargon (E2B, Flow Nexus) without explaining what those are or providing natural trigger terms users would use. The description needs explicit trigger guidance and broader keyword coverage.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about training ML models in sandboxes, distributed model deployment, or mentions Flow Nexus or E2B.'

Include natural keyword variations users would say, such as 'deep learning', 'machine learning', 'model training', 'GPU training', 'ML deployment'.

Expand the capability list with more specific actions, e.g., 'configure distributed training, monitor training runs, manage sandbox environments, deploy 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 but the core action description could conflict with general ML skills.	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.

This skill is highly actionable with concrete, executable MCP tool calls and complete examples, but it is severely bloated with repetitive content. Architecture examples appear twice, use cases duplicate earlier examples, and the entire document could be cut by 50%+ without losing information. The lack of bundle files means everything is packed into one massive file with no progressive disclosure, and workflows lack explicit validation checkpoints for distributed operations.

Suggestions

Reduce the document by at least 50%: remove the duplicated 'Architecture Patterns' section (already shown in examples), consolidate 'Common Use Cases' into the main examples, and trim response JSON examples to only one or two representative ones.

Split content into bundle files: move architecture reference to ARCHITECTURES.md, detailed API responses to API_REFERENCE.md, and common use cases to EXAMPLES.md, keeping SKILL.md as a concise overview with links.

Add explicit validation checkpoints to the distributed training workflow, e.g., 'Verify cluster status is ready before deploying nodes' and 'Check node health before starting training'.

Remove explanatory text Claude already knows (e.g., 'Best for: Classification, regression' for feedforward networks, descriptions of what LSTM or transformers are).

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. Response JSON examples add bulk without teaching Claude anything new. The 'Common Use Cases' section largely duplicates earlier examples with minor variations. Claude doesn't need explanations like 'Best for: Classification, regression, simple pattern recognition' for feedforward networks.	1 / 3
Actionability	The skill provides fully concrete, executable MCP tool calls with complete parameter structures, specific response schemas, and copy-paste ready examples covering training, inference, cluster management, and marketplace operations. Every capability is demonstrated with real tool invocations.	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. The troubleshooting section is separate and reactive rather than integrated into workflows. For destructive operations like cluster termination, there's no confirmation or validation step.	2 / 3
Progressive Disclosure	Everything is crammed into a single monolithic file with no bundle files to offload content. The architecture patterns, common use cases, and detailed API examples could easily be split into separate reference files. The 'Related Skills' and 'Resources' sections reference external links but the body itself is a wall of repetitive content that should be distributed across supporting files.	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/agentic-flow
Commit: 6a06854

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