Memory Guide

Define rule-driven long-term memory handling for AI agents via save_memory.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rocky2431/hiveclaw --skill memory-guide-rocky2431
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Memory Guide
Source: https://github.com/rocky2431/hiveclaw/tree/main/backend/app/templates/system_skills/memory-guide
Command: npx skills add https://github.com/rocky2431/hiveclaw --skill memory-guide-rocky2431

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines and enforces safe, rule-driven long-term memory handling for AI agents.

Core Features & Use Cases

  • Deterministic guidance: outlines exactly when manual memory interventions are appropriate and how to perform them via save_memory.
  • Guardrails for the memory pyramid: describes T0, T2, T3 flows, heartbeat curation, and soul.md integration.
  • Safe override protocol: explains how to bypass heartbeat filtering only with proper procedures.

Quick Start

Use save_memory with the appropriate category to directly write important facts to long-term memory.

Frequently Asked Questions about Memory Guide

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

FAQPage Schema
How do I enforce safe long-term memory handling for AI agents across sessions?

Safe long-term memory handling for AI agents requires rule-driven guardrails that dictate exactly when agents can read or edit memory across sessions. This ensures traceability and governance by preventing off-pipeline writes.

What is the memory pyramid and how does it manage AI agent memory flows?

The memory pyramid structures AI agent memory into T0, T2, and T3 flows with heartbeat curation and soul.md integration. It provides a tiered governance framework to securely manage long-term contextual data.

When should I manually intervene and write facts to long-term AI memory?

Manual memory interventions are appropriate when you need to persist important facts deterministically. You perform these direct writes by using the save_memory function with the appropriate category.

Can I bypass heartbeat filtering to override AI memory governance rules?

You can bypass heartbeat filtering only by following a strict safe override protocol. This ensures that governance, security, and traceability are maintained when deviating from standard memory curation.

How do I prevent off-pipeline memory writes in my AI application?

Preventing off-pipeline memory writes involves defining specific frontmatter fields, roles, and usage guidelines. This enforces deterministic writes and stops unauthorized memory modifications outside the pipeline.

Does implementing memory governance require specific frontmatter fields?

Implementing memory governance requires specifying frontmatter fields and roles to define usage guidelines. This structure enforces deterministic saves and secures interactions with the memory pyramid.