flow-nexus-neural

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

2.07x

Quality

59%

Does it follow best practices?

Impact

79%

2.07x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/flow-nexus-neural/SKILL.md

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is rich in concrete, executable MCP examples and well organized by section, but it functions as a monolithic API catalog rather than a skill overview. Verbatim duplicated examples, missing validation checkpoints around destructive cluster operations, and a complete absence of progressive disclosure (no reference files, everything inlined) are the main weaknesses.

Suggestions

Split the detailed tool catalog (Sections 3-6) into reference files (e.g. references/clusters.md, references/marketplace.md) and keep SKILL.md as a concise overview with one-level-deep pointers.

Add validation checkpoints before destructive operations, e.g. verify cluster status and training progress before terminate, mirroring the validate-then-proceed pattern.

Deduplicate the LSTM and transformer configs that appear verbatim in both the Examples and Common Use Cases / Architecture Patterns sections, referencing one canonical instance instead.

Dimension	Reasoning	Score
Conciseness	The body is mostly API detail Claude could not know, but it is noticeably redundant: the full LSTM config (lines 88-107) and transformer config (lines 113-133) are repeated verbatim in "Common Use Cases" (lines 556-575) and "Architecture Patterns" (lines 644-655). Mostly usable but clearly could be tightened, matching anchor 3; the duplication keeps it above 4.	3 / 5
Actionability	Concrete, complete MCP tool invocations with realistic configs and response payloads cover the common cases. Minor gaps keep it below 5: placeholder "your_user_id" values, and the GAN example uses pseudocode ("generator_layers: [...]").	4 / 5
Workflow Clarity	The cluster workflow (init, deploy nodes, connect, train, monitor, terminate) is clearly sequenced with status monitoring, but destructive and batch operations (cluster terminate, distributed training) have no validation checkpoints before proceeding, which per the guidelines caps workflow clarity at 3.	3 / 5
Progressive Disclosure	There are no bundle files at all (no references/, scripts/, or assets/), and ~740 lines of full API reference are inlined in SKILL.md with zero pointers to separate files — content that clearly belongs in reference files is entirely inlined, matching anchor 2 despite good section headers.	2 / 5
	Total	12 / 20 Passed

Description

65%Weight 40%Scale 1-5

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 specific and highly distinctive thanks to the Flow Nexus/E2B niche, with solid natural trigger terms. Its main weaknesses are the complete absence of any "when to use this" guidance and somewhat thin action coverage relative to what the skill actually does (inference, clusters, marketplace).

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to train, deploy, or benchmark neural networks via Flow Nexus or mentions distributed/federated training in E2B sandboxes."

Include one or two more concrete actions (e.g. run inference, set up distributed training clusters) to broaden capability coverage.

Add common synonyms such as "deep learning" or "model training" to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Train and deploy neural networks" names the domain and two concrete actions, matching the anchor for 1-2 concrete actions without comprehensive coverage; it omits inference, clustering, and marketplace capabilities, so it does not reach level 4's 'several specific actions'.	3 / 5
Completeness	It has a clear "what" (train and deploy neural networks in E2B sandboxes via Flow Nexus) but entirely lacks a "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Good keyword coverage with natural terms users would say ("train", "deploy", "neural networks", "distributed"), though common variations like "deep learning", "machine learning", or "model training" are missing, placing it just below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	"in distributed E2B sandboxes with Flow Nexus" carves out a clear niche with product-specific triggers that no generic ML or sandbox skill would match, minimizing conflict risk.	5 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: ruvnet/ruflo
Path: .agents/skills/flow-nexus-neural/SKILL.md
Commit: b14c79e

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.