flow-nexus-neural

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

2.07x

Quality

57%

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

65%

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

The body is highly actionable with complete, executable MCP tool calls, but it is verbose and monolithic — architecture examples and full JSON responses are repeated, no content is offloaded to reference files, and risky multi-step workflows lack validation checkpoints.

Suggestions

Add explicit validation/recovery checkpoints (validate cluster status before terminating, verify training status before publishing) for the distributed training and publishing workflows.

Split the exhaustive API reference and architecture patterns into separate reference files (e.g. REFERENCE.md, ARCHITECTURES.md) and keep SKILL.md as a concise overview with one-level-deep links.

Deduplicate the repeated LSTM/transformer examples and trim full JSON response payloads to the essential fields to reduce token cost.

Dimension	Reasoning	Score
Conciseness	It avoids explaining concepts Claude already knows, but ~720 lines carry heavy redundancy — the LSTM/transformer architecture examples recur across three sections and every endpoint ships a full JSON response payload that could be trimmed.	2 / 3
Actionability	Provides concrete, copy-paste-ready mcp__flow-nexus__* calls with complete argument objects, realistic parameter values, and inline options enumerated as comments.	3 / 3
Workflow Clarity	Multi-step sequences (init cluster, deploy nodes, train, monitor, terminate) are present, but batch/destructive operations like distributed training, cluster termination, and publishing lack explicit validation checkpoints or validate-fix-retry feedback loops, capping this at 2.	2 / 3
Progressive Disclosure	No bundle files exist and the ~720-line API reference is entirely inline in SKILL.md with section structure but no offloading to reference files; content that should be separate is inline.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 third-person and names a specific platform, but it lists only two actions and lacks an explicit 'Use when' trigger clause, leaving the 'when' dimension implied. Coverage of natural trigger terms and concrete capabilities is partial.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when training or deploying neural networks, running distributed model training, or working with Flow Nexus E2B sandboxes.'

Expand the action list to reflect concrete capabilities such as inference, template marketplace, distributed clusters, and federated learning.

Include common user-facing terms like 'deep learning', 'distributed training', and 'model deployment' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (neural networks, distributed E2B sandboxes) and two actions (train, deploy) but does not enumerate the concrete capabilities (inference, templates, clusters, federated learning) shown in the body.	2 / 3
Completeness	Clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Contains relevant natural terms ('neural networks', 'train', 'deploy') but omits common variations a user would actually say such as 'deep learning', 'distributed training', or 'model training'.	2 / 3
Distinctiveness Conflict Risk	The Flow Nexus / E2B sandbox framing is a distinct niche, but the broad 'neural networks' training domain overlaps with general ML/deep-learning skills.	2 / 3
	Total	8 / 12 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/claude-flow
Path: .agents/skills/flow-nexus-neural/SKILL.md
Commit: 26c35b5

Reviewed: about 4 hours 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.