Menú
Use when an agent needs to build or query the portable `.aoa` SQLite search index for archived Codex sessions, with evidence refs and freshness checks.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | aoa-session-search |
| description | Use when an agent needs to build or query the portable `.aoa` SQLite search index for archived Codex sessions, with evidence refs and freshness checks. |
| license | Apache-2.0 |
| metadata | {"aoa_scope":"session-memory","aoa_invocation_mode":"manual"} |
Use this skill for a bounded cross-session archive query or an explicitly requested portable search-projection refresh. Do not use it when current owner source, a typed entity route, or live runtime state already answers the question.
Search results are navigation. Raw, segment, session, receipt, and owner refs remain the evidence handoff.
<workspace-root> and <aoa-root>.python3 scripts/aoa_session_memory.py search \
--workspace-root <workspace-root> \
--aoa-root <aoa-root> \
--query "<bounded-query>" \
--explain
Use exactly one shallow reference when needed:
session_label, an event or segment identity, resolvable
evidence refs, and freshness.fresh hits as current routing evidence. Reindex or inspect raw
when stale or unverifiable.Stop after a bounded result set, honest miss, or one exact stale-provider recovery route. Do not widen from a successful typed route into broad FTS, run maintenance implicitly, claim storage improvement without before/after evidence, or treat a search hit as reviewed truth.
Use when a `.aoa` session-memory root must be created, installed, checked, repaired, or prepared for Codex hook-based session archiving.
Use when an indexed `.aoa` session needs provisional first-pass distillation into lessons, decisions, failures, and automation candidates without promoting them to reviewed truth.
Use when an agent needs evidence from prior `.aoa` sessions about how a skill, MCP, hook, tool, API, goal, eval, test, validator, script, decision, error, receipt, or other recurring operational entity was used, what happened nearby, and which raw or segment refs prove it.
Use in any Codex session when the user mentions `.aoa`, session memory, Codex transcripts, compaction, prior session rehydration, hook failures, or AoA session-memory validation.
Use when the live Codex PreCompact and PostCompact hook path must be proven through `.aoa` using the Codex app-server compact probe.
Use when AoA Codex hooks must be inspected, trusted, or compared against expected `.aoa` commands in the native Codex hook registry.