CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-memory-mcp

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

72

8.00x
Quality

58%

Does it follow best practices?

Impact

96%

8.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/agent-memory-mcp/SKILL.md

The canonical home for this skill is agent-memory-mcp in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

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

The content is concise and actionable with concrete setup commands and MCP tool signatures, but workflow clarity is held back by absent validation checkpoints and a meaningless 'When to Use' section.

Suggestions

Add verification checkpoints after each setup step, e.g. confirm 'npm run compile' succeeded and that the MCP server responds before declaring setup complete.

Replace the vacuous 'When to Use' section with concrete guidance on when to invoke memory_search/write/read versus the dashboard.

Show how to register the MCP server with the agent (e.g. the mcp config entry) so the start-server command is fully end-to-end runnable.

DimensionReasoningScore

Conciseness

The body is lean with executable commands and no over-explanation of concepts Claude knows; the only padding is the vacuous 'When to Use' line ('applicable to execute the workflow or actions described in the overview'), keeping it at anchor 4 rather than 5.

4 / 5

Actionability

Concrete, runnable commands ('git clone ...', 'npm install', 'npm run start-server <project_id> <absolute_path>') and MCP tool args with usage examples are mostly executable, with the minor gap that MCP-server registration with the agent is not shown, fitting anchor 4.

4 / 5

Workflow Clarity

Setup is a clear numbered sequence (clone, install, compile, start-server) but has no validation checkpoints (e.g. verify the server is running) and the 'When to Use' step is incoherent, matching anchor 3 (steps present, checkpoints missing/implicit).

3 / 5

Progressive Disclosure

The body is self-contained with well-signaled sections (Prerequisites, Setup, Capabilities, Dashboard) and no nested references; it slightly exceeds the 50-line simple-skill threshold and points to an external repo rather than bundle files, so anchor 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

48%Weight 40%Scale 1-5

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 clearly states what the skill does and targets a distinct niche, but it lacks explicit trigger guidance and concrete action verbs, capping completeness and trigger quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when an agent needs to persist, search, or recall architecture decisions, patterns, or project knowledge across sessions.'

Replace generic verbs ('provides ... knowledge management') with concrete actions users would invoke: 'store, search, read, and recall agent memories.'

Include common natural synonyms ('remember', 'recall', 'memory bank') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Quotes 'hybrid memory system that provides persistent, searchable knowledge management' name the domain but the only actions ('provides', 'searchable') are generic, matching anchor 2 rather than 3 which requires concrete actions like search/write/read.

2 / 5

Completeness

The 'what' is clear ('persistent, searchable knowledge management for AI agents') but there is no 'Use when...' clause, so per the guideline a missing trigger clause caps completeness at 3 (anchor 3: clear what, when missing).

3 / 5

Trigger Term Quality

'memory', 'knowledge management', 'Architecture, Patterns, Decisions' are relevant keywords but common natural variations users would say ('remember this', 'save a memory', 'recall') are missing, fitting anchor 3.

3 / 5

Distinctiveness Conflict Risk

'hybrid memory system ... for AI agents (Architecture, Patterns, Decisions)' carves a clear niche with only minor overlap risk against generic note/knowledge skills, matching anchor 4.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.