agent-v3-memory-specialist
Agent skill for v3-memory-specialist - invoke with $agent-v3-memory-specialist
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-v3-memory-specialist31
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/skillValidation 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 a technical identifier and invocation instruction, providing zero information about capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Stores and retrieves conversation context, manages long-term memory, tracks user preferences across sessions').
Include an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to remember something, recall previous conversations, or manage persistent information').
Remove or relocate the invocation syntax ('$agent-v3-memory-specialist') to a separate field, as it provides no value for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for v3-memory-specialist' is completely abstract and provides no information about what the skill actually does. | 1 / 3 |
Completeness | Missing both 'what' and 'when'. The description only provides an invocation command but explains neither what the skill does nor when Claude should use it. | 1 / 3 |
Trigger Term Quality | Contains only technical jargon ('v3-memory-specialist', '$agent-v3-memory-specialist') that users would never naturally say. No natural keywords related to memory, storage, recall, or any domain-specific terms. | 1 / 3 |
Distinctiveness Conflict Risk | While the technical identifier is unique, the description provides no semantic information to distinguish it from other skills. Claude cannot determine when to select this over any other skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a project specification document than an actionable skill for Claude. It's heavily padded with conceptual explanations, ASCII diagrams, and high-level descriptions that don't provide concrete guidance. The code examples are illustrative rather than executable, and the workflow lacks validation checkpoints critical for a complex migration task.
Suggestions
Remove conceptual explanations (mission statements, ASCII diagrams showing 'current vs target') and replace with executable commands and concrete code snippets
Split content into SKILL.md overview with references to separate files: MIGRATION.md, BENCHMARKS.md, SONA_INTEGRATION.md
Add explicit validation steps within each migration phase (e.g., 'After SQLite migration, run: npx validate-migration --source sqlite --verify-count')
Replace illustrative TypeScript classes with actual executable scripts or commands that Claude can run immediately
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive ASCII diagrams, mission statements, and explanatory content Claude doesn't need. The 'Systems to Unify' section explains what memory systems are rather than how to unify them. Much content describes concepts rather than providing actionable instructions. | 1 / 3 |
Actionability | Contains TypeScript code examples and SQL snippets that show structure, but they're illustrative rather than executable. The migration phases are high-level descriptions ('Week 3: AgentDB adapter creation') rather than concrete commands or copy-paste ready code. | 2 / 3 |
Workflow Clarity | Migration phases are listed but lack explicit validation checkpoints. The 'Validation & Testing' section exists but doesn't integrate into the workflow steps. No feedback loops for error recovery during migration - just a checklist of success criteria at the end. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including detailed code examples, migration plans, and benchmarks that could be split into separate reference documents. No navigation structure or links to detailed materials. | 1 / 3 |
Total | 6 / 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.