initializing-memory

Initialize deeply nested agent memory structures with YAML frontmatter files.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/AlvinPlayz23/boose --skill initializing-memory-alvinplayz23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: initializing-memory
Source: https://github.com/AlvinPlayz23/boose/tree/main/src/skills/builtin/initializing-memory
Command: npx skills add https://github.com/AlvinPlayz23/boose --skill initializing-memory-alvinplayz23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive guide for initializing or reorganizing agent memory. Load this skill when running /init, when the user asks you to set up your memory, or when you need guidance on creating effective memory files.

Core Features & Use Cases

  • Creates a clearly structured, deeply hierarchical memory filesystem under the agent's memory root
  • Specifies conventions for files (2-3 levels, 15-25 files) and YAML frontmatter (description, limit)
  • Supports reorganization workflows for new and existing agents, onboarding, and evolving memory needs

Quick Start

Create a deeply nested memory structure under system/ with 15-25 files across 2-3 levels, each file containing YAML frontmatter with a description and a limit, and organize domains such as human, project, and persona.

Frequently Asked Questions about initializing-memory

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

FAQPage Schema
How do I set up hierarchical agent memory for persistent context across sessions?▼

To set up hierarchical agent memory, initialize a deeply nested memory filesystem under the agent's memory root. This organizes 15-25 files across 2-3 levels under system/ and related root directories, ensuring persistent context across sessions.

What is the best way to organize agent memory files for onboarding?▼

The best way to organize agent memory is by creating a deeply nested structure with 15-25 files across 2-3 levels. Organize domains such as human, project, and persona under system/ to ensure consistent onboarding and evolving memory needs.

Do I need YAML frontmatter in every agent memory file?▼

Yes, every agent memory file requires YAML frontmatter containing a description and a limit. This convention ensures future memory updates remain consistent across the deeply nested filesystem structure.

Can I reorganize memory files for an existing agent?▼

Yes, you can reorganize memory for existing agents. The memory setup guide applies to both new and existing agents, orchestrating a deeply nested structure of 15-25 files to support evolving memory needs.

When should I initialize a nested memory filesystem for my agent?▼

You should initialize a nested memory filesystem when running /init, when asked to set up agent memory, or when needing guidance on creating effective memory files. It enables persistent context across sessions.

What directories should I create when structuring agent memory?▼

You should create directories under system/ and related root directories. Organize 15-25 files into 2-3 levels within this structure, establishing domains like human, project, and persona for comprehensive memory organization.