agent-memory-coordinator

Agent skill for memory-coordinator - invoke with $agent-memory-coordinator

1.53x

Quality

Does it follow best practices?

Impact

95%

1.53x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-memory-coordinator/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 critically deficient across all dimensions. It provides no information about what the skill does, when it should be used, or what user requests should trigger it. It reads as a placeholder rather than a functional description.

Suggestions

Add concrete actions describing what memory-coordinator does (e.g., 'Stores, retrieves, and organizes conversation context and user preferences across sessions').

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

Replace the invocation instruction ('invoke with $agent-memory-coordinator') with functional details — invocation syntax belongs in the skill body, not the description used for skill selection.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for memory-coordinator' is entirely abstract with 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 it's an agent skill and how to invoke it, with no functional or trigger information.	1 / 3
Trigger Term Quality	The only keyword is 'memory-coordinator', which is technical jargon unlikely to be used naturally by users. No natural trigger terms are present.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it's impossible to distinguish from any other memory-related or coordination-related skill. 'Memory-coordinator' could overlap with many potential skills.	1 / 3
	Total	4 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is almost entirely descriptive rather than instructive. It reads like a product feature overview or architecture document, listing capabilities and concepts without providing any concrete, executable guidance on how to actually perform memory operations. The content is heavily padded with generic software engineering concepts (caching, sharding, encryption, compliance) that Claude already knows and that aren't tied to any specific tooling or implementation.

Suggestions

Replace abstract descriptions with concrete, executable commands or tool invocations that Claude can actually use to store, retrieve, and manage memory (e.g., specific MCP tool calls, file operations, or API endpoints).

Define a clear step-by-step workflow for common memory operations (e.g., 1. Check namespace → 2. Store with key format → 3. Verify storage → 4. Handle errors) with explicit validation checkpoints.

Remove sections that describe concepts Claude already knows (security best practices, caching strategies, scalability patterns) and focus only on project-specific implementation details.

Add concrete examples with actual input/output showing exact key formats, data structures, and tool responses rather than natural language prompts like 'Remember that we're using PostgreSQL'.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive sections on concepts Claude already understands (caching strategies, security compliance, scalability patterns). Most content is abstract description rather than actionable instruction. The file is padded with generic software engineering concepts that don't teach Claude anything new.	1 / 3
Actionability	No executable code, no concrete commands, no specific tool invocations. The 'Usage Examples' are natural language prompts, not actionable instructions. Memory patterns show abstract YAML-like structures but nothing Claude can actually execute. There are no real APIs, commands, or concrete steps to perform memory operations.	1 / 3
Workflow Clarity	No clear multi-step workflow is defined. The skill describes what memory operations exist (store, retrieve, search, delete, sync) but never shows how to actually perform them in sequence. No validation checkpoints, no error recovery steps, no concrete process to follow.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files and no bundle files provided. All content is inline regardless of relevance, mixing high-level overview with detailed subsections on security, compliance, scalability, and caching that could be separated. No navigation structure or cross-references.	1 / 3
	Total	4 / 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/claude-flow
Commit: d29d87f

Reviewed: 4 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.