agent-swarm-memory-manager

Agent skill for swarm-memory-manager - invoke with $agent-swarm-memory-manager

2.25x

Quality

Does it follow best practices?

Impact

90%

2.25x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-swarm-memory-manager/SKILL.md

Quality

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an extremely weak description that fails on every dimension. It provides no information about what the skill does, when to use it, or what problems it solves — only an invocation command. It is essentially unusable for skill selection among multiple options.

Suggestions

Add concrete actions describing what swarm-memory-manager does (e.g., 'Manages shared memory across multiple agents, stores and retrieves coordination state, tracks task assignments').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when coordinating between agents, sharing state across swarm tasks, or managing multi-agent memory').

Remove the invocation instruction from the description (it belongs elsewhere) and replace it with functional content that distinguishes this skill from other agent or memory-related skills.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. It only states it is an 'agent skill for swarm-memory-manager' without describing what it actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only provides an invocation command, not functional information or usage triggers.	1 / 3
Trigger Term Quality	The only keyword is 'swarm-memory-manager', which is a technical/internal name, not a natural term a user would say. There are no natural language trigger terms like 'memory', 'shared state', 'coordination', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it provides no distinguishing characteristics. Without knowing what the skill does, it cannot be differentiated from any other agent skill.	1 / 3
	Total	4 / 12 Passed

Implementation

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

This skill is a verbose, aspirational description of a distributed memory management system that provides no actually executable guidance. It mixes pseudo-JavaScript with MCP tool call syntax in ways that cannot work, describes well-known CS concepts Claude already understands (CRDT, LRU, vector clocks), and includes fabricated metrics. The content reads more like a design document or wish list than an actionable skill.

Suggestions

Replace all pseudo-code with actual executable MCP tool calls showing the exact syntax Claude should use, removing the JavaScript async/await wrapper that cannot execute

Remove explanations of well-known concepts (CRDT, LRU, vector clocks, write-ahead logging) and focus only on the specific tool calls and key-naming conventions Claude needs to follow

Add a clear sequential workflow: 1) Initialize → 2) Index existing memory → 3) Monitor for updates → 4) Sync → 5) Validate consistency, with explicit validation checkpoints

Cut the content by at least 60% — remove fake metrics, abstract bullet-point sections, and integration points that provide no actionable information

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose and filled with concepts Claude already knows (caching levels, CRDT, vector clocks, LRU eviction). Much of the content describes abstract distributed systems concepts rather than providing actionable instructions. The code examples contain hardcoded fake metrics (operations_per_second: 1000, cache_hit_rate: 0.85) that are meaningless.	1 / 3
Actionability	The code examples are not executable — they mix JavaScript async/await syntax with MCP tool call pseudo-syntax in a way that cannot actually run. Functions like `resolveConflict` are referenced but never defined. The 'Cache Optimization' and 'Conflict Resolution' sections are purely descriptive bullet points with no concrete implementation.	1 / 3
Workflow Clarity	There is no clear sequenced workflow. The skill lists responsibilities and code snippets but never defines when or in what order operations should happen. Recovery procedures are vague bullet points with no steps. There are no validation checkpoints despite dealing with distributed state synchronization, which is inherently risky.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files and no bundle files to support it. All content is inline regardless of complexity, and there's no clear hierarchy between essential startup behavior and advanced features like conflict resolution or recovery.	1 / 3
	Total	4 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Commit: 2b9e2de

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.