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 list enough concrete actions 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 pipeline', 'machine learning', 'GPU training', 'model deployment'.

List more specific concrete actions beyond 'train and deploy', such as 'configure distributed training jobs, monitor training progress, manage sandbox environments, scale model inference'.

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, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also thin, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant terms 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 as product-specific identifiers, but 'train and deploy neural networks' is broad enough to overlap with other ML/AI-related 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.

The skill is highly actionable with concrete, executable MCP tool call examples covering a wide range of capabilities. However, it is extremely verbose and repetitive — architecture examples appear twice, common use cases largely duplicate earlier sections, and response JSON schemas inflate the document significantly. The content would benefit enormously from splitting into a concise overview SKILL.md with references to detailed sub-documents for architectures, distributed training, and marketplace operations.

Suggestions

Split the content into a concise SKILL.md overview (~100 lines) with references to separate files like ARCHITECTURES.md, DISTRIBUTED.md, MARKETPLACE.md, and EXAMPLES.md

Remove the duplicated Architecture Patterns section since each architecture is already demonstrated in the training examples above

Remove the Common Use Cases section or move it to a separate EXAMPLES.md — it largely repeats earlier content

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

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~500+ lines with massive repetition. Architecture patterns are shown in full examples AND repeated again in the 'Architecture Patterns' section. Common use cases duplicate earlier examples. The 'Best for:' descriptions for each architecture are things Claude already knows. Many response JSON examples add bulk without teaching anything new.	1 / 3
Actionability	Every capability includes fully concrete, copy-paste-ready MCP tool calls with complete parameter objects. Response schemas are shown as JSON. The examples cover all major use cases with specific configurations, making it very clear exactly what to call and with what arguments.	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 between steps. The troubleshooting section is separate and reactive rather than integrated into the workflow. For operations involving distributed cluster management, the lack of 'verify before proceeding' steps is a gap.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with everything inline. The Architecture Patterns, Common Use Cases, and detailed examples for every single tool could easily be split into separate reference files. The 'Related Skills' and 'Resources' sections at the bottom hint at external references but the body itself has no progressive disclosure — it dumps everything at once.	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: ccb062f

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.