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 findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-memory-coordinator/SKILL.md

Quality

Content

0%Scale 1-3

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 and conceptual rather than instructional. It reads like a product requirements document or feature overview for a memory system, not an actionable skill that teaches Claude how to perform specific tasks. There are no concrete tools, commands, APIs, or executable examples — just abstract descriptions of what a memory coordination system would ideally do.

Suggestions

Replace abstract descriptions with concrete, executable instructions showing exactly which tools/commands Claude should use to store, retrieve, and search memory (e.g., specific MCP tool calls or file-based memory operations).

Define a clear step-by-step workflow for core operations (store, retrieve, sync) with validation checkpoints, rather than listing conceptual features.

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

Add concrete input/output examples showing exact key formats, data structures, and expected responses for memory operations.

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 skill 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 YAML-like pseudo-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 a memory system conceptually does but never specifies how Claude should actually perform memory operations step by step. No validation checkpoints, no error recovery, no sequenced process for any operation.	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 depth or relevance. Sections like Security & Privacy and Performance Optimization are abstract filler that could be removed entirely, let alone split into separate files.	1 / 3
	Total	4 / 12 Passed

Description

0%Scale 1-3

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 label with an invocation command rather than a functional description. It fails on every dimension: it provides no concrete actions, no natural trigger terms, no guidance on when to use it, and nothing to distinguish it from other skills. It is one of the weakest possible skill descriptions.

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 context, or manage stored information.'

Include domain-specific keywords users would naturally say, such as 'remember', 'recall', 'save context', 'notes', 'memory', 'previous conversation'.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for memory-coordinator' is entirely vague 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. There is no 'Use when...' clause and no description of functionality.	1 / 3
Trigger Term Quality	The only keyword is 'memory-coordinator', which is technical jargon unlikely to be used naturally by users. There are no natural trigger terms a user would say.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it could conflict with any memory-related or coordination-related skill. There are no distinct triggers to differentiate it.	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
Path: .agents/skills/agent-memory-coordinator/SKILL.md
Commit: 913f9ea

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.