Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector s...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill agent-memory-systems37
Quality
11%
Does it follow best practices?
Impact
76%
1.10xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/agent-memory-systems/SKILL.mdDiscovery
0%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 like an academic introduction rather than a functional skill description. It focuses on conceptual framing ('cornerstone', 'architecture') instead of actionable capabilities, contains no trigger terms users would naturally use, and is truncated mid-word. The description fails to help Claude distinguish when to select this skill over others.
Suggestions
Replace philosophical framing with concrete actions: 'Store and retrieve information across conversations, manage persistent notes, search saved knowledge' instead of 'cornerstone of intelligent agents'
Add explicit trigger guidance: 'Use when the user asks to remember something, save notes, recall previous information, or manage persistent knowledge'
Include natural user keywords: 'remember', 'save', 'notes', 'recall', 'look up', 'stored information', 'knowledge base'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract, philosophical language ('cornerstone of intelligent agents', 'architecture of agent memory') without listing any concrete actions Claude can perform. No specific capabilities like 'store', 'retrieve', 'search', or 'update' are mentioned. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (covers architecture of memory) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains technical jargon ('vector s...', 'context window') that users wouldn't naturally say. Missing natural trigger terms like 'remember', 'recall', 'save information', 'notes', or 'knowledge base'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'memory' and 'intelligent agents' could apply to virtually any skill involving data persistence, context management, or knowledge retrieval. High conflict risk with many potential skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a skeleton with headers but no substantive content. The patterns, anti-patterns, and sharp edges sections are either empty or contain placeholder text. While the organizational structure shows intent, the complete lack of actionable guidance, code examples, or actual workflow definitions makes this skill unusable in its current form.
Suggestions
Add concrete, executable code examples for each memory pattern (e.g., vector store initialization, chunking implementation, retrieval queries)
Fill in the Pattern sections with actual step-by-step implementation guidance, not just headers
Replace placeholder 'Issue' text in Sharp Edges table with actual problems and provide complete solutions, not just section headers
Add specific examples showing memory retrieval strategies with actual code for at least one vector database
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The introduction has some unnecessary narrative framing ('You are a cognitive architect...'), but the overall structure attempts efficiency. However, the content is incomplete/truncated, making it hard to fully assess verbosity. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. Pattern sections are empty headers with no implementation details. The 'Sharp Edges' table has placeholder 'Issue' text instead of actual issues, and solutions are just headers without content. | 1 / 3 |
Workflow Clarity | No workflows are defined. Pattern sections are empty stubs without steps or sequences. There are no validation checkpoints or process flows for implementing any memory system. | 1 / 3 |
Progressive Disclosure | The structure attempts organization with sections for Patterns, Anti-Patterns, and Sharp Edges, and references related skills. However, the pattern sections are empty, and there are no links to detailed documentation or examples. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%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 | |
Table of Contents
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.