agent-v3-memory-specialist
Agent skill for v3-memory-specialist - invoke with $agent-v3-memory-specialist
33
0%
Does it follow best practices?
Impact
85%
1.77xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-v3-memory-specialist/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 description is essentially a label and invocation command with zero functional content. It fails on every dimension: it does not describe what the skill does, when to use it, or include any natural trigger terms. It would be impossible for Claude to reliably select this skill from a list of available skills.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Stores, retrieves, and manages persistent memory entries across conversations' or whatever the actual capabilities are.
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to remember something, recall previous context, manage memory, or store/retrieve information.'
Remove the invocation command from the description (it's metadata, not a description) and replace with meaningful capability and context information.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for v3-memory-specialist' is entirely abstract and gives no indication of what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states the invocation command, providing no functional or contextual information. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say. 'v3-memory-specialist' is internal jargon, and 'invoke with $agent-v3-memory-specialist' is a technical invocation command, not a trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it provides no distinguishing characteristics. 'Memory specialist' could overlap with any skill involving memory, storage, caching, or knowledge management without any clarity on its niche. | 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 reads as a project planning document or architectural design spec rather than an actionable skill for Claude. It is extremely verbose, repeating performance claims throughout, and contains no executable code or concrete step-by-step instructions. The content would need to be fundamentally restructured from a design document into actionable guidance with real commands, validation steps, and appropriate content splitting.
Suggestions
Replace the architectural design sketches with concrete, executable commands and code that Claude can actually run to perform memory migration tasks.
Reduce the content by 70-80% — remove ASCII diagrams, repeated performance claims, project timeline information, and coordination points that don't help Claude execute tasks.
Add explicit step-by-step workflows with validation checkpoints (e.g., 'run this command, check this output, if error do X') instead of high-level phase descriptions.
Split detailed content (SONA integration, migration scripts, benchmarking) into separate referenced files and keep SKILL.md as a concise overview with clear navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~250+ lines. Contains extensive ASCII diagrams, marketing-style claims ('150x-12,500x' repeated 6+ times), project management content (phases, weeks, coordination points), and conceptual explanations that don't provide actionable guidance. Much of this is aspirational documentation rather than executable skill instructions. | 1 / 3 |
Actionability | Despite containing TypeScript and SQL code blocks, none are executable — they are illustrative pseudocode/design sketches for classes that don't exist yet. The migration phases use bash code blocks that are actually bullet-point lists, not commands. There are no concrete, copy-paste-ready instructions Claude could follow to accomplish any specific task. | 1 / 3 |
Workflow Clarity | The migration strategy lists phases at a high level (Week 3, Week 4-5, Week 6) but provides no concrete step-by-step workflow with validation checkpoints. The 'Validation & Testing' section contains a benchmark class skeleton but no actual validation steps integrated into the workflow. Success criteria are a checklist of outcomes, not process steps. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content — architecture, migration, SONA integration, benchmarks, coordination — is inlined in a single massive document. No navigation structure or links to separate detailed guides for the distinct concerns covered. | 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/claude-flow
- Commit
0d9f9b1
- 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.