flow-nexus-neural

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

2.63x

Quality

37%

Does it follow best practices?

Impact

95%

2.63x

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, and misses common user-facing trigger terms like 'machine learning', 'deep learning', or 'model training'.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user wants to train or deploy machine learning models, neural networks, or deep learning pipelines in sandboxed environments.'

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

Expand the capability list with more specific actions, e.g., 'configure distributed training jobs, monitor training progress, deploy trained models to endpoints, manage sandbox environments'.

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 relevant terms 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 examples covering the full API surface. However, it is extremely verbose and repetitive, with architecture examples duplicated across sections and no content split into supporting files. Workflow sequences exist but lack explicit validation checkpoints and error-recovery loops that would be important for distributed training operations.

Suggestions

Eliminate duplicate architecture examples—show each architecture once in the Architecture Patterns section and reference it from other sections instead of repeating full code blocks.

Split detailed content into bundle files: move Architecture Patterns to ARCHITECTURES.md, Common Use Cases to EXAMPLES.md, and API response schemas to API_REFERENCE.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, confirm all nodes are 'active' before starting training).

Remove response JSON examples that Claude can infer from context, or consolidate them into a single API reference file.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~500+ lines. Massive amounts of repetitive code examples (e.g., LSTM architecture appears three separate times). The 'Architecture Patterns' section near the end duplicates examples already shown in the core capabilities section. Response JSON examples add bulk without adding clarity Claude couldn't infer. The 'Common Use Cases' section largely repeats earlier examples with minor variations.	1 / 3
Actionability	Every capability includes concrete, executable MCP tool calls with full parameter specifications and expected response JSON. The examples are copy-paste ready with realistic configurations, and cover the full lifecycle from setup to training to inference to termination.	3 / 3
Workflow Clarity	The distributed training section has a clear 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 node deployment succeeded before proceeding). The troubleshooting section is separate rather than integrated into workflows.	2 / 3
Progressive Disclosure	This is a monolithic wall of content with no bundle files to offload detail into. The architecture patterns, common use cases, and detailed API examples could all be split into separate reference files. Everything is inline in one massive document with no meaningful progressive disclosure structure—just a flat list of sections.	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 (757 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/ruvector
Commit: c2089c4

Reviewed: 1 day 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.