agent-memory-mcp

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

8.00x

Quality

41%

Does it follow best practices?

Impact

96%

8.00x

Average score across 3 eval scenarios

Securityby

Critical

Do not install without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/agent-memory-mcp/SKILL.md

Quality

Discovery

17%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description reads more like a product tagline than a functional skill description. It lacks concrete actions, natural trigger terms, and any explicit guidance on when Claude should select this skill. The parenthetical hints at scope but doesn't compensate for the overall vagueness.

Suggestions

Add explicit trigger guidance: 'Use when the user asks to remember, recall, or look up project decisions, architectural patterns, or previously discussed topics.'

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

Include natural user-facing trigger terms like 'remember this', 'what did we decide', 'save decision', 'project notes', 'look up pattern'.

Dimension	Reasoning	Score
Specificity	Names the domain ('memory system', 'knowledge management') and hints at what it stores ('Architecture, Patterns, Decisions'), but doesn't list concrete actions like 'store decisions', 'search patterns', 'retrieve architecture notes'.	2 / 3
Completeness	Describes what it is at a high level but has no 'Use when...' clause or equivalent explicit trigger guidance. The 'when' is entirely missing, which per the rubric caps completeness at 2, and the 'what' is also vague enough to warrant a 1.	1 / 3
Trigger Term Quality	Uses technical/abstract terms like 'hybrid memory system', 'persistent, searchable knowledge management', and 'AI agents' which are not natural phrases a user would say. Missing common trigger terms like 'remember', 'save note', 'look up decision', 'project memory'.	1 / 3
Distinctiveness Conflict Risk	The parenthetical '(Architecture, Patterns, Decisions)' provides some specificity, but 'knowledge management' and 'memory system' are broad enough to overlap with note-taking, documentation, or other memory-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

64%

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

The skill provides solid, actionable setup instructions and clear MCP tool documentation with concrete examples. Its main weaknesses are the lack of validation/verification steps in the workflow (e.g., confirming the server is running), a vacuous 'When to Use' section, and some minor verbosity in the introduction. The tool API documentation is well-structured and practical.

Suggestions

Add a verification step after starting the MCP server (e.g., 'Verify the server is running by calling memory_stats({}) — you should see an empty stats response').

Remove or replace the 'When to Use' section with actual guidance on when to invoke memory operations (e.g., 'Write a memory after making architecture decisions; search before starting new features to check for existing patterns').

Trim the opening paragraph — the YAML description already covers what the skill does; jump straight to Prerequisites or Setup.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary filler like 'This skill provides a persistent, searchable memory bank that automatically syncs with project documentation' which restates the description, and the 'When to Use' section is a meaningless tautology. The MCP tool docs are reasonably lean.	2 / 3
Actionability	Provides concrete, copy-paste-ready bash commands for setup, specific MCP tool signatures with argument types, and usage examples mapping natural language to tool calls. The setup steps are fully executable.	3 / 3
Workflow Clarity	Setup steps are 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 or the server doesn't respond, and no verification step after starting the MCP server.	2 / 3
Progressive Disclosure	Content is reasonably structured with clear sections, but everything is inline in one file. The dashboard section and detailed MCP tool reference could be split out. For a skill of this length (~80 lines), the organization is acceptable but the 'When to Use' section adds no value and there are no references to deeper documentation.	2 / 3
	Total	9 / 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: sickn33/antigravity-awesome-skills
Commit: d739c8b

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.