Multi-layer memory architecture for agents: short-term context, long-term vector storage, and retrieval optimization.
Works with
Covers seven memory types: short-term (context window), long-term (vector stores), working, episodic, semantic, and procedural memory, each suited to different information patterns
Provides three core patterns: memory type selection, vector store choice, and chunking strategy to maximize retrieval accuracy
Highlights critical retrieval challenges: contextual chunking,
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionagent-memory-systemsExecute the skills CLI command in your project's root directory to begin installation:
Fetches agent-memory-systems from sickn33/antigravity-awesome-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate agent-memory-systems. Access via /agent-memory-systems in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
31.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
31.1K
stars
You are a cognitive architect who understands that memory makes agents intelligent. You've built memory systems for agents handling millions of interactions. You know that the hard part isn't storing - it's retrieving the right memory at the right time.
Your core insight: Memory failures look like intelligence failures. When an agent "forgets" or gives inconsistent answers, it's almost always a retrieval problem, not a storage problem. You obsess over chunking strategies, embedding quality, and
Choosing the right memory type for different information
Choosing the right vector database for your use case
Breaking documents into retrievable chunks
| Issue | Severity | Solution |
|---|---|---|
| Issue | critical | ## Contextual Chunking (Anthropic's approach) |
| Issue | high | ## Test different sizes |
| Issue | high | ## Always filter by metadata first |
| Issue | high | ## Add temporal scoring |
| Issue | medium | ## Detect conflicts on storage |
| Issue | medium | ## Budget tokens for different memory types |
| Issue | medium | ## Track embedding model in metadata |
Works well with: autonomous-agents, multi-agent-orchestration, llm-architect, agent-tool-builder
This skill is applicable to execute the workflow or actions described in the overview.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
sickn33/antigravity-awesome-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
We added agent-memory-systems from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
agent-memory-systems is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in agent-memory-systems — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in agent-memory-systems — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
agent-memory-systems has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: agent-memory-systems is the kind of skill you can hand to a new teammate without a long onboarding doc.
agent-memory-systems fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for agent-memory-systems matched our evaluation — installs cleanly and behaves as described in the markdown.
agent-memory-systems has been reliable in day-to-day use. Documentation quality is above average for community skills.
agent-memory-systems reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 57