agent-v3-memory-specialist

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

1.77x

Quality

13%

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 about the skill's capabilities, domain, or trigger conditions. It fails on every dimension by offering only an internal agent name and invocation syntax, making it impossible for Claude to determine when to select this skill.

Suggestions

Describe what the skill actually does with concrete actions (e.g., 'Stores, retrieves, and manages persistent memory entries across conversations').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to remember something, recall previous context, or manage stored notes').

Remove the invocation syntax from the description and replace it with domain-specific keywords that distinguish this skill from other potentially similar skills.

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 skill's internal name and invocation syntax.	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, context, storage, or recall without any clarifying scope.	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 as a project planning/architecture document rather than an actionable skill for Claude. It is extremely verbose, mixing high-level strategy, week-by-week timelines, coordination notes, and illustrative (but non-executable) code into a single monolithic file. The content would benefit enormously from being condensed to core actionable instructions with detailed references split into separate files.

Suggestions

Reduce the skill body to under 80 lines focusing only on the concrete steps Claude should take when invoked, moving architecture details, migration plans, and benchmarks to separate referenced files (e.g., ARCHITECTURE.md, MIGRATION.md, BENCHMARKS.md).

Replace illustrative TypeScript classes with executable code or specific CLI commands that Claude can actually run, or clearly mark them as design specifications rather than executable examples.

Add explicit validation checkpoints within the migration workflow (e.g., 'After migrating SQLite data, run X to verify row counts and embedding integrity before proceeding').

Remove project management content (week timelines, coordination points, success criteria checklists) that describes team processes rather than instructing Claude on what to do.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~250+ lines. Includes extensive ASCII diagrams, project management details (week-by-week plans, coordination points, success criteria checklists), and conceptual explanations that don't provide actionable guidance Claude couldn't infer. Much of this is planning documentation rather than a skill.	1 / 3
Actionability	Contains TypeScript code examples and SQL snippets that illustrate the architecture, but none are truly executable—they reference non-existent classes (AgentDBAdapter, HNSWIndexer, HNSWIndex), fictional npm packages (agentic-flow@alpha), and undefined interfaces. The code is closer to pseudocode/design docs than copy-paste ready implementations.	2 / 3
Workflow Clarity	Migration phases are listed in sequence (Phase 1-3) with rough timelines, but validation checkpoints are only mentioned as success criteria checkboxes at the end rather than integrated into the workflow. There's no explicit feedback loop for error recovery during migration steps, and the benchmark validation is described but not woven into the process.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content—architecture, migration plans, benchmarks, SONA integration, coordination points—is inlined in a single massive document. There's no separation of overview from detailed reference material, and no navigation aids or links to supplementary docs.	1 / 3
	Total	6 / 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: 398f7c2

Reviewed: 3 days 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.