memory

Divide memory into a durable USER profile and token-budgeted MEMORY context.

79|9|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/RikyZ90/ShibaClaw --skill memory-rikyz90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/RikyZ90/ShibaClaw/tree/main/shibaclaw/skills/memory
Command: npx skills add https://github.com/RikyZ90/ShibaClaw --skill memory-rikyz90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Divide memory into a durable USER profile and a token-budgeted MEMORY context. The HISTORY.md logs provide an append-only trace while updates to MEMORY.md are truncated to fit token budgets.

Core Features & Use Cases

  • Durable USER.md profile stores long-lived user facts and preferences.
  • memory/MEMORY.md provides the operational short-term context injected into prompts under a token budget.
  • memory/HISTORY.md acts as an append-only log for traceability and retrospective analysis.

Quick Start

Create USER.md for a durable profile and memory/MEMORY.md for current task context within the token budget.

Frequently Asked Questions about memory

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

FAQPage Schema
How do I manage AI context across sessions without exceeding the token budget?

Splitting memory into a durable USER.md profile for long-lived facts and a token-budgeted MEMORY.md for operational context manages AI context without exceeding the token budget. This division retains essential user data while keeping recent decisions constrained within fixed token limits.

What is memory compaction for AI agents and how does it preserve essential data?

Memory compaction is the automatic truncation of operational context in MEMORY.md to fit a fixed token budget. It preserves essential data by retaining critical recent decisions while discarding obsolete details, ensuring the AI agent stays within its operational constraints.

How do I set up durable user profiles and short-term context for AI agents?

Create a USER.md file for long-lived user facts and preferences, and a memory/MEMORY.md file for current task context to set up durable user profiles and short-term context. This structure separates persistent profile data from operational memory injected into prompts.

Can I keep an append-only history log for AI agent traceability and retrospective analysis?

You can keep an append-only history log for AI agent traceability by using memory/HISTORY.md. This log acts as a trace for retrospective analysis, recording sequential updates while the operational MEMORY.md context is truncated to fit token budgets.

What is the best way to structure long-lived user facts separately from recent AI decisions?

Dividing memory into a durable USER.md profile and a token-budgeted MEMORY.md context is the best way to structure long-lived user facts separately from recent AI decisions. This approach isolates permanent preferences from volatile operational data and history logs.