mailbox

Store per-agent findings, context, and standing orders across sessions.

116|56|Updated Jan 18, 2026

Search Tags:#context #persistence #agent-memory #mailbox #standing-orders #spawn-prompt

Ready to run

npx skills add https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli --skill mailbox

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mailbox
Source: https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli/tree/main/src/skills/mailbox
Command: npx skills add https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli --skill mailbox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Persistent agent mailbox provides a durable memory layer for team agents, enabling findings, context, and standing instructions to survive across sessions.

Core Features & Use Cases

Persist across sessions: store agent findings and context in a durable mailbox.
Per-agent control: manage standing orders, read latest findings, and archive sessions for team handoffs.
Spawn-ready context: pre-load memory into agent prompts to improve continuity between runs.

Quick Start

Run the mailbox.sh script to manage persistent agent memory across sessions.

Frequently Asked Questions about mailbox

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

FAQPage Schema

How do I persist agent memory across multiple sessions?▼

To persist agent memory across sessions, use a durable mailbox that stores per-agent findings, context, and standing orders under a dedicated directory path. It enables read, write, load, archive, and list operations to maintain continuity and handoffs between runs.

What is the best way to manage standing orders for AI agents?▼

Managing standing orders for AI agents requires per-agent storage that survives session terminations. A persistent mailbox enforces dedicated directories to store and load these instructions, ensuring agents retrieve and apply consistent operational directives across executions.

How do I pre-load context into agent prompts for better continuity?▼

Pre-loading context into agent prompts involves reading previously archived findings and memory from a durable mailbox before spawning the agent. This spawn-ready approach injects historical session context directly into the prompt to improve cross-session continuity.

Can I use shell scripts to manage cross-session context for team workflows?▼

Yes, you can use shell scripts to manage cross-session context for team workflows. The mailbox functionality is driven by a shell script that handles memory management operations, enabling team handoffs and per-agent data isolation without requiring external dependencies.

How does append-only logging work for agent findings and handoffs?▼

Append-only logging for agent findings works by continuously adding new context entries to a durable storage file without overwriting previous records. This creates an immutable historical trail that supports accurate session archiving and team handoffs.

Does persistent agent memory require external databases or dependencies?▼

No, persistent agent memory does not require external databases or dependencies. The mailbox enforces per-agent storage directly within the local file system using shell scripts, ensuring durable context and findings persistence without complex setup.