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 label with invocation syntax 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 no distinguishing characteristics. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.

Suggestions

Describe the concrete actions this skill performs (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').

Remove the invocation syntax ('invoke with $agent-memory-coordinator') from the description and replace it with capability and trigger information that helps Claude decide when to select this skill.

Dimension	Reasoning	Score
Specificity	The description contains 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 overlap with any memory-related or coordination-related skill. 'Memory-coordinator' provides minimal distinctiveness without explaining what kind of memory or coordination is involved.	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 abstract description and taxonomy with no actionable content. It reads like a product requirements document or feature wishlist rather than an executable skill that teaches Claude how to perform memory coordination. There are no concrete tools, APIs, commands, or code examples that Claude could actually use.

Suggestions

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

Define a clear step-by-step workflow for core operations like 'store project context' with validation checkpoints (e.g., verify data was stored, confirm retrieval matches)

Remove sections Claude already knows about (caching strategies, security compliance, scalability patterns) and focus only on project-specific memory system details and conventions

Move advanced/reference content (security, performance optimization, integration patterns) to separate files and link from a concise overview

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. Operations like Store, Retrieve, Search, Delete, and Sync are listed as bullet points without any sequencing, validation steps, or error handling. There's no concrete process for how to actually perform memory coordination tasks.	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 & Privacy, and Performance Optimization sections add bulk without clear navigation or separation into referenced documents.	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/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.