agent-memory-systems
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 stores), and the cognitive architectures that organize them. Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets. The field is fragm
Overall
score
22%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill agent-memory-systemsActivation
0%This description reads like an educational essay or documentation about memory concepts rather than a functional skill description. It lacks any concrete actions, explicit trigger conditions, or practical guidance for when Claude should select this skill. The text is also truncated, suggesting incomplete content.
Suggestions
Replace conceptual explanations with concrete actions (e.g., 'Store and retrieve information across conversations, manage vector embeddings, query long-term memory stores').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to remember something, recall previous information, or manage persistent data').
Remove educational content about memory architecture and focus on what the skill enables Claude to do, ensuring the description is complete and not truncated.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract, conceptual language ('cornerstone of intelligent agents', 'cognitive architectures') without listing concrete actions Claude can perform. No specific capabilities like 'create', 'retrieve', 'store', or 'query' are mentioned. | 1 / 3 |
Completeness | The description explains conceptual background about memory systems but never answers 'what does this skill do' in actionable terms or 'when should Claude use it'. There is no 'Use when...' clause or equivalent trigger guidance. The text also appears truncated ('The field is fragm'). | 1 / 3 |
Trigger Term Quality | Contains technical jargon ('vector stores', 'chunking', 'embedding') that users wouldn't naturally say. Missing natural trigger terms like 'remember', 'recall', 'save information', or 'look up'. The terms used are academic rather than user-facing. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so abstract and conceptual that it's unclear what specific task domain it covers. 'Memory' and 'agents' are extremely broad terms that could overlap with many other skills. No distinct triggers are provided. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
15%This skill is essentially a skeleton with placeholder content. It has section headers suggesting a comprehensive memory systems guide, but the actual content is missing - patterns have no implementations, anti-patterns have no explanations, and the sharp edges table contains broken/placeholder data. The philosophical framing adds tokens without providing actionable guidance.
Suggestions
Add concrete code examples for each memory pattern (e.g., vector store initialization, chunking implementation, retrieval queries)
Fix the Sharp Edges table - replace 'Issue' placeholders with actual issues and provide real solutions instead of section headers
Flesh out the Pattern sections with actual implementation guidance, including specific libraries (LangChain, LlamaIndex, etc.) and executable code
Add a Quick Start section with a minimal working example of implementing agent memory
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content has some unnecessary narrative framing ('You are a cognitive architect...') and repetitive philosophical statements about memory. The capabilities list is bloated with 10 items that could be consolidated. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable guidance. Pattern sections are empty headers with no implementation details. The 'Sharp Edges' table has broken content with 'Issue' placeholders and solutions that appear to be section headers rather than actual solutions. | 1 / 3 |
Workflow Clarity | No clear workflows or step-by-step processes are defined. Pattern sections are empty stubs. There are no validation checkpoints or sequences for implementing memory systems. | 1 / 3 |
Progressive Disclosure | The content is poorly organized with empty sections, a malformed table, and no references to detailed documentation. The structure suggests content should exist but it's missing entirely. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
50%Validation — 8 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_voice | 'description' should use third person voice; found second person: 'you can' | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 8 / 16 Passed | |
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.