memory-loader

Loads agent memory layers and verifies vault infrastructure at session start.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/joydai2026-del/skills --skill memory-loader-joydai2026-del
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-loader
Source: https://github.com/joydai2026-del/skills/tree/main/memory-loader
Command: npx skills add https://github.com/joydai2026-del/skills --skill memory-loader-joydai2026-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents lose context between sessions, leading to repeated mistakes, stale assumptions, and re-done work. This Skill enforces a mandatory session-start protocol that restores memory before any work begins. ## Core Features & Use Cases - Bounded memory loading: Reads context.md, corrections, session index, and pattern cards with strict token budgets so nothing is silently truncated. - Vault infrastructure verification: Checks symlinks, git remotes, disk space, and shared-memory routing before work starts. - Learning journal creation: Opens or creates a dated learning journal for real-time logging of mistakes, corrections, and wins. - Use Case: At the start of a coding session, run the protocol to load your agent's context, the other agent's context, unresolved corrections, and recent session history, then reply with a one-line memory-loaded receipt. ## Quick Start Tell the agent to run the memory-loader session start protocol and confirm what it remembers before beginning any work.

Frequently Asked Questions about memory-loader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I give an AI agent persistent memory across sessions?▼

Use a session-start protocol that reads bounded slices of stored context: a capped context.md, the last few corrections, the newest session-index entries via tail, and active pattern cards. The agent confirms loading with a one-line receipt.

How to load agent context without exceeding token limits?▼

Bound every read: cap context.md at a fixed size, tail the session index instead of reading it whole, and load only the last five corrections plus unresolved ones. Full files are read only on explicit search.

Can multiple agents share the same memory store?▼

Yes. Corrections, session index, patterns, and decisions load from shared paths via a memory-store helper, while context.md, identity.md, and learning journals stay per-agent. Each agent also reads the other agent's context.md for cross-agent visibility.

What happens if memory files are missing or stale?▼

A missing or unreadable file is noted, not treated as a failure, and the protocol continues. If the last session is over 7 days old, memory is flagged stale and stored facts are treated as hypotheses; over 30 days triggers a consolidation suggestion.

When should the memory loading protocol run?▼

Run it at the start of every substantive session, when resuming after a gap, when switching projects mid-session, or when a prompt carries a handoff from another agent or surface. It must complete before any work begins.