agent-swarm-memory-manager
Agent skill for swarm-memory-manager - invoke with $agent-swarm-memory-manager
34
0%
Does it follow best practices?
Impact
90%
2.25xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-swarm-memory-manager/SKILL.mdQuality
Discovery
0%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 all dimensions. It provides only the skill's internal name and invocation command without any explanation of capabilities, use cases, or trigger conditions. It is essentially a label, not a description.
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 multiple agents, sharing state across swarm tasks, or managing distributed memory').
Replace the invocation instruction with functional language in third person voice that helps Claude understand when to select this skill over others.
| 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's impossible to differentiate it from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%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 rather than an actionable skill. The code examples are non-executable pseudocode that mixes incompatible syntaxes, the concepts described (CRDT, vector clocks, multi-level caching) are abstract descriptions Claude already knows, and there is no clear workflow or validation process. The skill reads more like a design document than operational instructions.
Suggestions
Replace all pseudocode with actual executable MCP tool calls showing the exact syntax for store/retrieve operations, removing the fake JavaScript wrapper functions
Define a clear sequential workflow: 1) Initialize memory namespace, 2) Set up sync manifest, 3) Monitor and update metrics—with explicit validation at each step
Remove explanations of well-known distributed systems concepts (CRDT, vector clocks, LRU, write-ahead logging) and replace with specific implementation details unique to this system
Split advanced topics (conflict resolution strategies, recovery procedures) into separate referenced files, keeping SKILL.md as a concise operational overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with many concepts Claude already understands (caching levels, CRDT, vector clocks, LRU eviction). The code examples are pseudocode dressed as JavaScript that isn't actually executable. Much of the content describes distributed systems concepts rather than providing actionable instructions. | 1 / 3 |
Actionability | The code examples are not executable—they mix MCP tool call syntax with JavaScript async/await in ways that cannot actually run. Functions like `resolveConflict` are referenced but never defined. The 'Cache Optimization' and 'Conflict Resolution' sections are bullet-point descriptions with no concrete implementation. | 1 / 3 |
Workflow Clarity | There is no clear sequential workflow. The skill describes many operations (initialize, sync, read, write, metrics) but never sequences them into a coherent process with validation checkpoints. Recovery procedures are listed as bullet points with no actual steps. No feedback loops or error handling workflows are defined. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files. All content—initialization, caching, sync, conflict resolution, metrics, recovery—is dumped into a single file with no clear navigation structure or separation of concerns. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
100%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/ruflo
- Commit
398f7c2
- Reviewed
Table of Contents
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.