agent-memory-coordinator
Agent skill for memory-coordinator - invoke with $agent-memory-coordinator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-memory-coordinator37
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 95%
↑ 1.53xAgent success when using this skill
Validation for skill structure
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 description is critically deficient across all dimensions. It functions only as an invocation reference rather than a proper skill description, providing no information about capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a skill library.
Suggestions
Add concrete actions describing what memory-coordinator does (e.g., 'Stores and retrieves conversation context, manages persistent memory across sessions, coordinates memory between agents').
Include a 'Use when...' clause with natural trigger terms users might say (e.g., 'Use when the user asks to remember something, recall previous conversations, or coordinate information between agents').
Remove the invocation syntax from the description field - this belongs in usage documentation, not the selection-focused description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for memory-coordinator' is completely abstract and does not describe what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides invocation syntax without explaining purpose or triggers. | 1 / 3 |
Trigger Term Quality | The only terms present are technical jargon ('agent skill', 'memory-coordinator', '$agent-memory-coordinator'). No natural keywords a user would say when needing memory coordination functionality. | 1 / 3 |
Distinctiveness Conflict Risk | While 'memory-coordinator' is a specific name, the description is so vague that it's unclear what domain this covers, making it impossible to distinguish from other potential memory or coordination skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is primarily conceptual documentation rather than actionable guidance. It describes what a memory coordination system should do without providing any concrete implementation details, executable code, or specific commands. The extensive sections on security, performance, and integration patterns explain concepts Claude already understands without adding project-specific value.
Suggestions
Replace conceptual descriptions with actual executable code showing how to store, retrieve, and search memory using the specific tools/APIs available in this system
Add concrete command examples or function calls instead of natural language prompts like 'Remember that we're using PostgreSQL...'
Create a clear step-by-step workflow for common memory operations with validation checkpoints (e.g., 'After storing, verify with: <specific command>')
Remove sections explaining general concepts (caching strategies, security principles) and focus only on project-specific implementation details
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive conceptual explanations Claude already knows (what memory operations are, what caching strategies mean, basic security concepts). The document is padded with organizational structure that adds no actionable value. | 1 / 3 |
Actionability | No executable code, commands, or concrete implementation details. Examples like 'Remember that we're using PostgreSQL...' are vague natural language prompts, not actionable instructions. Memory patterns show structure but no actual implementation. | 1 / 3 |
Workflow Clarity | No clear step-by-step workflows for memory operations. Lists concepts like 'Store', 'Retrieve', 'Search' without explaining how to actually perform these operations. No validation checkpoints or error handling procedures. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but everything is in one monolithic file. No references to external documentation for detailed implementations. The structure exists but content that should be separate (security, performance, integration patterns) is all inline. | 2 / 3 |
Total | 5 / 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.
- 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.