agent-v3-memory-specialist

Agent skill for v3-memory-specialist - invoke with $agent-v3-memory-specialist

1.77x

Quality

Does it follow best practices?

Impact

85%

1.77x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-v3-memory-specialist/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 description is essentially a placeholder that provides no useful information for skill selection. It fails on every dimension: it describes no concrete actions, includes no natural trigger terms, answers neither 'what' nor 'when', and offers no distinguishing characteristics. Claude would have no basis for selecting this skill appropriately from a pool of available skills.

Suggestions

Replace the entire description with concrete actions the skill performs, e.g., 'Stores, retrieves, and manages persistent memory entries across conversations. Handles memory creation, updates, deletion, and search.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to remember something, recall previous information, manage notes, or work with persistent memory/knowledge.'

Remove the invocation instruction ('invoke with $agent-v3-memory-specialist') from the description, as it is operational metadata and not useful for skill selection.

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 how to invoke the agent, not what it does or when it should be selected.	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' is undefined and could overlap with any skill involving memory, storage, caching, or knowledge management.	1 / 3
	Total	4 / 12 Passed

Implementation

12%

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 targets throughout, and contains no executable code—only aspirational TypeScript classes referencing non-existent libraries. The content would benefit from being drastically reduced to concrete, actionable instructions with real commands and validated code examples.

Suggestions

Replace aspirational TypeScript classes with actual executable code or concrete CLI commands that Claude can run—if the libraries don't exist yet, the skill should focus on what can be done now.

Reduce content by 70-80%: remove repeated performance claims, ASCII diagrams, coordination points, and project timeline sections that don't provide actionable guidance.

Split the monolithic content into separate files (e.g., MIGRATION.md, BENCHMARKS.md, SONA.md) and provide a concise overview in SKILL.md with clear references.

Add concrete validation steps with feedback loops: e.g., after migration, run a specific verification command, check output, and define what to do if validation fails.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~250+ lines. Includes extensive ASCII diagrams, aspirational performance claims repeated multiple times (150x-12,500x appears 5+ times), project management timelines, and coordination points that are not actionable instructions. Much of this is descriptive/planning content rather than teaching Claude how to do something.	1 / 3
Actionability	Despite containing TypeScript and SQL code blocks, none are executable—they reference non-existent classes (AgentDBAdapter, HNSWIndexer, HNSWIndex), fictional npm packages (agentic-flow@alpha), and undefined interfaces. The code is aspirational design documentation, not concrete guidance Claude can act on. Migration phases are described as bash comments, not actual commands.	1 / 3
Workflow Clarity	There is a phased migration strategy (Phase 1-3) with some sequencing, and a validation section with success criteria checklist. However, the phases contain no real validation checkpoints—they're high-level project plans ('Week 3: AgentDB adapter creation') rather than step-by-step workflows with feedback loops. The benchmark code is illustrative but not tied to a concrete validation workflow.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files and no bundle files provided. All content—architecture, migration plans, SONA integration, benchmarks, coordination points—is inlined in a single massive document with no clear navigation hierarchy or separation of concerns.	1 / 3
	Total	5 / 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/ruflo
Commit: 619b263

Reviewed: about 10 hours 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.