SkillAgentSearch skills...

Agent Memory Architecture

Complete zero-dependency memory system for AI agents — file-based architecture, daily notes, long-term curation, context management, heartbeat integration, and memory hygiene. No APIs, no databases, no external tools. Works with any agent framework.

Install / Use

npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-agent-memory

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Universal

Our assessment of Agent Memory Architecture

Agent Memory Architecture scores 90/100 on our quality scale, 306th of 604 Data & Analytics skills we index.

Its SKILL.md is 17 KB long, well organised into 91 sections with 18 code examples: a thorough specification that gives an agent plenty to work with.

With 2,149 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
14/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-10-30 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

Agent Memory Architecture compared with similar skills

All 4 of these similar skills score higher than Agent Memory Architecture; compare them before choosing.

SkillScoreStarsUpdatedFormat
Agent Memory Architecture (this skill)by LeoYeAI902.1k4mo agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server
crawl4aiby unclecode10087.4k3d agoMCP Server

Frequently asked questions

How do I install Agent Memory Architecture?
Run npx skills add LeoYeAI/openclaw-master-skills --skill "Agent Memory Architecture". The install tabs above show the steps for each supported agent.
Which AI agents does Agent Memory Architecture work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is Agent Memory Architecture safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is Agent Memory Architecture still maintained?
The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: Agent Memory Architecture description: Complete zero-dependency memory system for AI agents — file-based architecture, daily notes, long-term curation, context management, heartbeat integration, and memory hygiene. No APIs, no databases, no external tools. Works with any agent framework. metadata: category: agent skills: ["memory", "agent", "context", "persistence", "knowledge-management", "openclaw", "productivity"]

Agent Memory Architecture

Complete memory system for AI agents using only files. No APIs. No databases. No external dependencies. Just smart file structures and disciplined practices that give your agent perfect recall.


1. Memory Architecture Overview

workspace/
├── MEMORY.md              ← Long-term curated memory (the brain)
├── ACTIVE-CONTEXT.md      ← Hot working memory (what matters NOW)
├── AGENTS.md              ← Operating manual (how you work)
├── memory/
│   ├── 2026-01-15.md      ← Daily notes (raw event log)
│   ├── 2026-01-16.md
│   ├── heartbeat-state.json  ← Heartbeat tracking state
│   ├── topics/
│   │   ├── project-alpha.md  ← Topic-specific deep context
│   │   ├── client-acme.md
│   │   └── tech-stack.md
│   └── archive/
│       ├── 2025-Q4.md       ← Quarterly archive summaries
│       └── 2025-Q3.md

The 5 Memory Layers

| Layer | File | Purpose | Read Frequency | Write Frequency | |-------|------|---------|----------------|-----------------| | 1. Hot | ACTIVE-CONTEXT.md | Current priorities, blockers, in-flight work | Every session | Multiple times/day | | 2. Warm | MEMORY.md | Curated long-term knowledge, decisions, people | Every main session | Weekly curation | | 3. Daily | memory/YYYY-MM-DD.md | Raw event log, conversations, actions taken | Today + yesterday | Throughout the day | | 4. Topic | memory/topics/.md | Deep context on specific subjects | When topic comes up | As knowledge grows | | 5. Cold | memory/archive/.md | Historical summaries, rarely accessed | On explicit search | Quarterly rollup |

Core Principle: Write It Down

Memory is limited. Files are permanent.

  • "Mental notes" don't survive session restarts. Files do.
  • If someone says "remember this" → write to a file
  • If you learn a lesson → update the relevant file
  • If you make a mistake → document it so future-you doesn't repeat it
  • Text > Brain 📝

2. Layer 1: Hot Memory (ACTIVE-CONTEXT.md)

Your working scratchpad. What's happening RIGHT NOW.

Template

# ACTIVE-CONTEXT.md — What's Hot

Last updated: 2026-01-15 14:30 GMT

## 🔥 Current Priority
[ONE sentence: what is the most important thing right now?]

## In Progress
- [ ] Task A — status, next step
- [ ] Task B — status, blocker

## Waiting On
- Waiting for [person] to [action] — asked [date]
- Waiting for [system] to [complete] — ETA [time]

## Key Decisions Made Today
- Decided to [X] because [Y] — reversible: yes/no

## Context for Next Session
[What does future-you need to know to pick up where you left off?]

Rules

  • Max 50 lines — if it's longer, you're hoarding. Move completed items to daily notes.
  • Update before ending session — your gift to future-you
  • One priority — if everything is priority, nothing is
  • Delete completed items — this is NOT an archive

3. Layer 2: Long-Term Memory (MEMORY.md)

Your curated brain. Distilled knowledge, not raw logs.

Structure Template

# MEMORY.md — Long-Term Memory

## About [Human]
- Name, preferences, timezone, communication style
- What motivates them, what frustrates them
- Key relationships, roles, goals

## About Me [Agent]
- Name, personality, capabilities
- Operating preferences learned over time

## Active Projects
### Project Name
- Status, key decisions, blockers
- Links to relevant topic files

## Key People
- [Name] — role, relationship, communication notes

## Lessons Learned
- [Date] — [What happened] → [What I learned]

## Preferences & Patterns
- [Human prefers X over Y]
- [This approach works better than that one]

## Important Dates
- [Event] — [Date] — [Context]

Curation Rules

  1. Only curated insights — not raw events (those go in daily notes)
  2. Review weekly — scan daily notes, extract what's worth keeping
  3. Prune quarterly — remove outdated info, archive completed projects
  4. Max 500 lines — if it's longer, you need topic files
  5. Security — never store secrets, API keys, passwords
  6. Main session only — don't load MEMORY.md in group chats or shared contexts

What Goes In vs What Doesn't

| ✅ Goes in MEMORY.md | ❌ Stays in daily notes | |----------------------|------------------------| | "Kalin prefers being told, not asked" | "Today Kalin said he prefers being told" | | "Apollo.io free plan doesn't support API" | "Tried Apollo.io API, got 403 error" | | "Client AcmeCo — $50K deal, Q2 close" | "Sent AcmeCo the proposal at 3pm" | | "Always verify prospect names with live search" | "Found 6/18 prospect names were wrong" |


4. Layer 3: Daily Notes (memory/YYYY-MM-DD.md)

Raw event log. Everything that happened today.

Template

# 2026-01-15 — Daily Notes

## Morning
- [08:15] Started session, reviewed ACTIVE-CONTEXT
- [08:30] Received task from [human]: [summary]
- [09:00] Completed [task] — result: [outcome]

## Afternoon
- [14:00] [Event/conversation summary]
- [15:30] Decision: [what was decided and why]

## Key Takeaways
- [Anything worth remembering beyond today]

## Tomorrow
- [ ] Follow up on [X]
- [ ] Check [Y]

Rules

  • One file per day — memory/YYYY-MM-DD.md
  • Append-only during the day — don't edit earlier entries
  • Timestamps for important events
  • Summarize, don't transcribe — capture essence, not every word
  • Auto-create the memory/ directory if it doesn't exist
  • Retention: Keep 30 days of daily notes. Archive older ones quarterly.

5. Layer 4: Topic Files (memory/topics/*.md)

Deep context on specific subjects that span many days.

When to Create a Topic File

  • A project lasts more than 2 weeks
  • A client/person comes up frequently
  • A technical area needs accumulated knowledge
  • You keep searching daily notes for the same information

Template

# [Topic Name]

Created: YYYY-MM-DD
Last updated: YYYY-MM-DD

## Summary
[2-3 sentences: what is this about?]

## Key Facts
- [Fact 1]
- [Fact 2]

## Decision Log
| Date | Decision | Reasoning | Outcome |
|------|----------|-----------|---------|
| | | | |

## Open Questions
- [Question 1]

## Related
- memory/topics/[related-topic].md
- [External link]

Rules

  • Name descriptively — project-alpha.md not topic-1.md
  • One topic per file — if it covers two things, split it
  • Link from MEMORY.md — topic files are extensions of long-term memory
  • Update when you learn — don't let them go stale

6. Layer 5: Archive (memory/archive/*.md)

Historical summaries for completed projects and past quarters.

Quarterly Archive Process

Every quarter (or when daily notes exceed 30 files):

  1. Read all daily notes older than 30 days
  2. Extract key events, decisions, outcomes, lessons
  3. Write memory/archive/YYYY-QN.md (e.g., 2025-Q4.md)
  4. Delete or move archived daily notes
  5. Update MEMORY.md if any long-term insights emerged

Archive Template

# Q4 2025 Archive

## Summary
[3-5 sentences: what defined this quarter?]

## Major Events
- [Event 1] — [outcome]
- [Event 2] — [outcome]

## Projects
### [Project Name]
- Started: [date], Ended: [date]
- Outcome: [result]
- Lesson: [what we learned]

## Metrics
- [Key metric 1]: [value]
- [Key metric 2]: [value]

## Lessons Carried Forward
- [Lesson added to MEMORY.md: yes/no]

7. Session Startup Protocol

What to read at the start of every session, in order:

Main Session (Direct Chat with Human)

1. SOUL.md          — Who am I? (personality, values)
2. USER.md          — Who am I helping? (human context)
3. MEMORY.md        — Long-term memory (full brain)
4. ACTIVE-CONTEXT.md — Hot working memory (current state)
5. memory/today.md  — Today's daily notes (if exists)
6. memory/yesterday.md — Yesterday's notes (recent context)

Shared/Group Session (Discord, Slack, Group Chats)

1. SOUL.md          — Who am I?
2. USER.md          — Who am I helping?
3. ACTIVE-CONTEXT.md — Current priorities only
4. memory/today.md  — Today's notes
⚠️ DO NOT load MEMORY.md — contains private context

Sub-Agent / Isolated Session

1. Task-specific context only
2. Relevant topic file if applicable
3. ACTIVE-CONTEXT.md for current state
⚠️ Minimal context = focused output + lower token cost

8. Memory Write Protocol

When to Write (Triggers)

| Event | Action | Target File | |-------|--------|-------------| | Session starts | Log start time | Daily notes | | Task completed | Log result + outcome | Daily notes | | Decision made | Log decision + reasoning | Daily notes + topic file | | Lesson learned | Log lesson | Daily notes → MEMORY.md | | Person mentioned with new info | Update person section | MEMORY.md or topic file | | Human says "remember this" | Write immediately | MEMORY.md | | Session ends | Update ACTIVE-CONTEXT | ACTIVE-CONTEXT.md | | Weekly review | Curate MEMORY.md | MEMORY.md | | Quarterly | Archive old daily notes | Archive |

Write-Ahead Protocol

For critical information, write BEFORE acting:

1. Human gives important instruction
2. IMMEDIATELY write to daily notes or MEMORY.md
3. THEN execute the instruction
4. Update with results after

Why: If the session crashes mid-execution, the instruction is preserved.

Conflict Resolution

When information conflicts between layers:

  • ACTIVE-CONTEXT.md wins for current state (most recent)
  • MEMORY.md wins for long-term facts (curated)
  • Daily notes are evidence — use to resolve disputes
  • Topic files win for deep domain knowledge

9. Memory Search Strategy

When you need to find something:

Search Order (Fast to Slow)

1. ACTIVE-CONTEXT.md    — Is it current? (instant)
2. MEMORY.md            — Is it a known fact? (quick scan)
3. memory/today.md      — Did it happen today? (quick)
4. memory/yesterday.md  — Did it happen recently? (quick)
5. memory/topics/*.md   — Is it a deep topic? (targeted)
6. memory_search tool   — Semantic search across all files
7. memory/archive/*.md  — Is it historical? (slow)

Search Tips

  • Use memory_search tool for fuzzy/semantic queries
  • Use memory_get with line numbers for precise retrieval after search
  • Check daily notes in reverse chronological order
  • If you can't find it after 3 searches, ask the human

10. Memory Hygiene Schedule

Daily (During Session)

  • [ ] Read ACTIVE-CONTEXT.md at session start
  • [ ] Create/append to today's daily notes
  • [ ] Update ACTIVE-CONTEXT.md before session ends
  • [ ] Move completed ACTIVE-CONTEXT items to daily notes

Weekly (Pick One Heartbeat)

  • [ ] Read last 7 daily notes
  • [ ] Extract significant events/lessons to MEMORY.md
  • [ ] Prune ACTIVE-CONTEXT.md (remove stale items)
  • [ ] Check topic files for staleness
  • [ ] Review MEMORY.md for outdated information

Monthly

  • [ ] MEMORY.md line count check (target: <500 lines)
  • [ ] Topic files audit — any need merging or archiving?
  • [ ] Daily notes older than 30 days → archive
  • [ ] Check if any topic files should be promoted to MEMORY.md sections

Quarterly

  • [ ] Full archive process (see Layer 5)
  • [ ] MEMORY.md deep review — still accurate?
  • [ ] Topic files — archive completed projects
  • [ ] Update AGENTS.md with any process improvements learned

11. Heartbeat Integration

Use heartbeats (periodic agent wake-ups) for memory maintenance:

heartbeat-state.json

{
  "last_memory_review": "2026-01-15",
  "last_archive": "2025-12-31",
  "last_active_context_prune": "2026-01-14",
  "daily_notes_count": 12,
  "memory

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars2.1k
CategoryData
Updated3mo ago
Forks325

Languages

Python

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info