Name: agent-safla-neural
Rating: 48.8 (1 reviews)
Author: ruvnet

Blog Docs Log in Get started

agent-safla-neural

Agent skill for safla-neural - invoke with $agent-safla-neural

3.03x

Quality

20%

Does it follow best practices?

Impact

100%

3.03x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-safla-neural/SKILL.md

The canonical home for this skill is agent-safla-neural in ruvnet/claude-flow

Quality

Content

26%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 reads as a buzzword-heavy persona/capabilities manifesto rather than actionable skill guidance: its code examples are non-executable pseudocode, it has no workflow or validation steps, and it is a structureless monolith with an embedded duplicate frontmatter block. It explains concepts Claude already knows instead of adding unique, runnable know-how.

Suggestions

Replace the non-executable MCP pseudocode blocks with real, copy-paste-ready commands or tool calls, or explicitly label them as illustrative pseudocode.

Add a concrete step-by-step workflow with validation checkpoints (e.g., train -> store pattern -> verify recall -> adjust feedback loop) rather than a capabilities bullet list.

Trim unverifiable marketing claims and concept re-explanations (memory tiers, feedback loops) that Claude already understands, and remove the stray second frontmatter block at lines 6-10.

Dimension	Reasoning	Score
Conciseness	The body is padded with buzzword-laden capability claims ('truly intelligent, self-improving agents', 'quantum, and chaotic neural patterns', unverifiable figures like '60% compression' and '172,000+ operations per second') and re-explains memory-tier concepts Claude already knows.	2 / 5
Actionability	The MCP snippets give concrete-looking guidance, but 'mcp__claude-flow__neural_train { pattern_type: ... }' is not valid executable JavaScript — it is pseudocode presented as a code block with no call syntax — so guidance is present but incomplete and non-runnable.	3 / 5
Workflow Clarity	There is no multi-step process or sequence at all; the body is a persona description, a bullet list of capabilities, and a memory model, with no steps, ordering, or validation checkpoints.	1 / 5
Progressive Disclosure	The body is a flat monolith with no references to other files (and no references/scripts/assets bundle exists), a stray second YAML frontmatter block embedded mid-document, and only minimal section headers, so structure is minimal and inline content that could be split apart is not.	2 / 5
	Total	8 / 20 Passed

Description

15%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 frontmatter description is a near-empty placeholder: it states only that this is an agent skill for safla-neural and how to invoke it, with no concrete capabilities or usage triggers. It fails to tell a user or Claude what the skill does or when to use it.

Suggestions

Replace the description with concrete actions the skill performs (e.g., 'Designs multi-tiered memory architectures, engineers self-improving feedback loops, and orchestrates distributed neural training').

Add an explicit 'Use when...' trigger clause naming natural phrases a user would say (e.g., 'Use when the user asks about SAFLA, self-aware feedback loops, persistent neural memory, or distributed neural training').

Write the description in third-person active voice and drop the 'invoke with $...' syntax, which belongs in usage docs, not the skill description.

Dimension	Reasoning	Score
Specificity	The description 'Agent skill for safla-neural - invoke with $agent-safla-neural' names no concrete actions whatsoever; it is pure abstract language identifying only that this is a skill wrapper.	1 / 5
Completeness	There is only an extremely vague 'what' ('Agent skill for safla-neural') and no 'when' clause at all — 'invoke with $...' describes how to call it, not when Claude should use it, so both what and when are effectively missing.	1 / 5
Trigger Term Quality	The only keyword is the skill's own name 'safla-neural', and 'invoke with $agent-safla-neural' is a technical invocation instruction rather than a natural phrase a user would actually say when they need the skill.	2 / 5
Distinctiveness Conflict Risk	Although the phrasing 'Agent skill for X' is generic, the named domain 'safla-neural' anchors it to a specific niche, giving moderate distinctiveness despite some overlap risk with other agent-skill wrappers.	3 / 5
	Total	7 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Path: .agents/skills/agent-safla-neural/SKILL.md
Commit: fa13ee4

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