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 beyond 'train and deploy' and omits natural trigger terms users would actually use.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about training ML models in sandboxes, distributed deep learning, or deploying neural networks with Flow Nexus.'

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

List more specific concrete actions beyond 'train and deploy', e.g., 'configure distributed training across sandboxes, monitor training runs, manage model checkpoints, deploy inference 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 verbs.	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', 'distributed', and 'deploy', but 'E2B sandboxes' and 'Flow Nexus' are product-specific jargon that users may not naturally say. 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 general ML/AI skills. The product-specific terms help but the core action is generic.	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 complete parameter examples, which is its primary strength. However, it is severely bloated with extensive repetition (architectures shown 2-3 times each, use cases duplicating earlier examples) and lacks progressive disclosure — everything is crammed into one massive file. Workflow clarity is adequate but missing explicit validation checkpoints for distributed operations.

Suggestions

Eliminate duplicate content: architecture patterns appear in examples, in the 'Architecture Patterns' section, and again in 'Common Use Cases'. Keep one canonical example per architecture and reference it.

Split into multiple files: move distributed training, marketplace/templates, and architecture patterns into separate referenced documents (e.g., DISTRIBUTED.md, TEMPLATES.md, ARCHITECTURES.md) with brief summaries in the main skill.

Add explicit validation checkpoints to the distributed training workflow, e.g., verify cluster is 'ready' before deploying nodes, confirm all nodes are 'active' before starting training, validate training metrics before running inference.

Remove generic best practices that Claude already knows (e.g., 'start small', 'monitor training') and trim response JSON examples to only show non-obvious fields.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~500+ lines. Massive amounts of repetition — architecture patterns are shown multiple times (once in examples, again in 'Architecture Patterns' section, again in 'Common Use Cases'). The LSTM config appears at least 3 times. Response JSON examples add bulk without teaching Claude anything it couldn't infer from the API shape. Lists like 'Best Practices' contain generic advice Claude already knows.	1 / 3
Actionability	The skill provides fully concrete, copy-paste-ready MCP tool calls with complete parameter structures, specific architecture configs, and example responses. Every capability is demonstrated with executable code rather than abstract descriptions.	3 / 3
Workflow Clarity	The distributed training section has 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 the workflow. For operations involving distributed cluster management and resource allocation, missing validation steps cap this at 2.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with everything inlined. The 'Architecture Patterns' section duplicates content already shown in examples. The 'Common Use Cases' section repeats earlier examples with minor variations. There are references to related skills and external docs at the bottom, but the core content should be split — e.g., architecture patterns, distributed training, and marketplace usage could each be separate referenced 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/ruflo
Commit: 398f7c2

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.