Archival Recall

Insert and search Archival via one CLI language.

Skill metadata

Source	Bundled (installed by default)
Path	skills/memory/archival-recall
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	memory, archival, providers, search
Related skills	episodic-diary

Reference: full SKILL.md

info

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Archival Recall Skill

Use the Archival Memory OS tier for long-lived facts that must not bloat Core (MEMORY.md) or User (USER.md). One CLI language works with whatever external memory.provider is active — do not invent provider-specific tool names in recipes when the unified verbs suffice.

When to Use

• Fact is durable and may be needed weeks later, but Core is near its budget.
• User asks to “remember forever” something too long for prompt injection.
• Searching past preferences/decisions that live in the provider backend.

Do not use Archival for chat history (“what did we do last Tuesday”) — that is Episodic (vibeos memory episodes / session_search).

Prerequisites

• memory.provider set (vibeos memory setup / vibeos memory status).
• Provider credentials available (secrets in .env only).
• Built-in Core/User still active — Archival is additive.

How to Run

# Gap matrix (which native tool each provider maps to)
vibeos memory archival matrix

# Insert (unified)
vibeos memory archival insert "User prefers TypeScript strict mode on all repos."

# Search (unified)
vibeos memory archival search "TypeScript preferences" --limit 5 --json

In-chat, if provider tools are exposed, you may call the native tool shown by matrix — but prefer the CLI verbs above so recipes stay provider-agnostic.

Quick Reference

Verb	CLI	Native examples
insert	vibeos memory archival insert "…"	mem0_add, hindsight_retain, viking_remember
search	vibeos memory archival search "…"	mem0_search, hindsight_recall, viking_search
matrix	vibeos memory archival matrix	—

Pitfalls

• No external provider → configure one; do not remove Core char limits.
• Profiles are islands — Archival is per profile / provider config.
• After delegate_task, the parent may auto-promote findings into Archival + memories/proposed_core.jsonl (memory.delegation_promote). Leaves still cannot call memory.

Verification

• vibeos memory archival matrix lists the active provider’s tools.
• insert then search returns the fact (or provider-queued ack) with that provider.