agent-memory-mcp

A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

Quality

36%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/agent-memory-mcp/SKILL.md

Quality

Content

64%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 provides solid actionable setup instructions and clear MCP tool documentation with concrete examples. Its main weaknesses are generic boilerplate sections ('When to Use', 'Limitations') that waste tokens without adding value, and the lack of validation/verification steps in the setup workflow (e.g., confirming the server is running). The content is functional but could be tightened and made more robust.

Suggestions

Remove or replace the generic 'When to Use' and 'Limitations' sections with project-specific guidance (e.g., 'Use when you need to persist architectural decisions, patterns, or context across sessions').

Add a verification step after starting the MCP server (e.g., 'Verify the server is running: curl http://localhost:<port>/health or run memory_stats({}) to confirm connectivity').

Add brief error recovery guidance for common setup failures (e.g., port conflicts, missing Node.js version).

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some unnecessary filler. The 'When to Use' and 'Limitations' sections are generic boilerplate that add no real value. The MCP tool descriptions are reasonably concise but could be tightened (e.g., the natural language usage examples are somewhat redundant).	2 / 3
Actionability	Setup steps include concrete, copy-paste-ready bash commands. MCP tool documentation provides specific argument signatures with types and concrete usage examples showing exact function calls. The dashboard startup command is also fully executable.	3 / 3
Workflow Clarity	The setup workflow is clearly sequenced (clone → install → start), but there are no validation checkpoints — no way to verify the server started successfully, no error recovery guidance if npm install fails, and no verification step after setup. For a server-based tool, missing health checks or confirmation steps is a gap.	2 / 3
Progressive Disclosure	The content is reasonably organized with clear sections, but everything is in a single file with no references to external documentation. The tool reference section could be split out for a cleaner overview. With no bundle files provided, there's no supporting structure, though the skill is short enough that this is partially acceptable.	2 / 3
	Total	9 / 12 Passed

Description

7%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 reads more like a product tagline than a functional skill description. It relies on abstract concepts ('hybrid memory system', 'knowledge management') without specifying concrete actions or providing trigger guidance. The lack of a 'Use when...' clause and absence of natural user-facing keywords make it difficult for Claude to know when to select this skill.

Suggestions

Add a 'Use when...' clause with natural trigger terms like 'remember this', 'save this decision', 'look up architecture decisions', 'what patterns have we established'.

Replace abstract language with concrete actions, e.g., 'Stores and retrieves architecture decisions, design patterns, and project knowledge. Searches past decisions and patterns by keyword or topic.'

Include specific file types, commands, or interaction patterns that would help distinguish this from generic note-taking or documentation skills.

Dimension	Reasoning	Score
Specificity	The description uses abstract language like 'hybrid memory system', 'persistent, searchable knowledge management' without listing concrete actions. The parenthetical '(Architecture, Patterns, Decisions)' hints at categories but doesn't describe what the skill actually does (e.g., store decisions, search patterns, record architecture notes).	1 / 3
Completeness	The description partially addresses 'what' (knowledge management) but in very vague terms, and completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	The terms used ('hybrid memory system', 'knowledge management', 'AI agents') are technical jargon unlikely to match natural user requests. Users would more likely say things like 'remember this decision', 'save this pattern', 'look up what we decided', none of which are represented.	1 / 3
Distinctiveness Conflict Risk	The mention of 'memory system' and the specific categories (Architecture, Patterns, Decisions) provide some distinctiveness, but 'knowledge management' is broad enough to overlap with note-taking, documentation, or other memory-related skills.	2 / 3
	Total	5 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: popey/claude-code-skills
Path: skills/agent-memory-mcp/SKILL.md
Commit: a5a6601

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