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 essentially a placeholder that provides no useful information about the skill's capabilities or when it should be used. It fails on every dimension: no concrete actions, no natural trigger terms, no 'what' or 'when' guidance, and insufficient detail to distinguish it from other skills. It reads more like an invocation instruction than a functional description.

Suggestions

Describe what the skill actually does with concrete actions (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 conversations, or manage stored context').

Remove the invocation instruction ('invoke with $agent-memory-coordinator') from the description and replace it with functional details that help Claude select this skill appropriately.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for memory-coordinator' is entirely abstract and does not describe 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 a user. There are no natural trigger terms a user would say.	1 / 3
Distinctiveness Conflict Risk	The term 'memory-coordinator' is somewhat unique as a name, but the description is so vague that it's impossible to distinguish its purpose from any other memory-related or coordination-related skill.	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 reads as a high-level design document or feature wishlist rather than an actionable skill for Claude. It describes abstract concepts (namespaces, caching strategies, compliance, sharding) without providing any concrete tools, commands, APIs, or executable steps. Nearly every section lists categories and bullet points but never tells Claude *how* to actually perform memory operations.

Suggestions

Replace abstract descriptions with concrete, executable examples showing actual tool calls or commands for storing, retrieving, and searching memory (e.g., specific MCP tool invocations or API calls).

Define a clear step-by-step workflow for common memory operations (store, retrieve, search) with validation steps to confirm operations succeeded.

Remove sections Claude doesn't need (Security & Privacy compliance details, scalability architecture, caching strategy theory) and focus on what Claude should actually do when invoked.

Add references to external files for advanced topics (e.g., 'See INTEGRATION.md for cross-agent patterns') instead of inlining everything in one large document.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive sections on concepts Claude already understands (caching strategies, security compliance, scalability patterns). Most content is abstract categorization and listing rather than actionable instruction. The skill is padded with unnecessary organizational taxonomy that doesn't help Claude perform any concrete task.	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 code snippets to interact with any memory system.	1 / 3
Workflow Clarity	No clear multi-step workflow is defined. The skill lists capabilities and categories but never sequences them into a process. There are no validation checkpoints, no error recovery steps, and no concrete workflow for how to actually perform memory operations.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline regardless of depth or relevance. Advanced features, security, performance optimization, and integration patterns are all dumped into one file with no navigation structure or links to detailed resources.	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: 0d9f9b1

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.