一键导入
aippocampus
Use AIppocampus source-backed continuity through the repo MCP and CLI surfaces.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use AIppocampus source-backed continuity through the repo MCP and CLI surfaces.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Find source-backed continuity before important agent work: recover old wording, reopen routes, check handoffs/corrections/preferences, and help a fresh thread continue from local source.
Review, shape, or implement AIppocampus agent-facing UX for foreground recall, hooks, MCP/CLI tools, action cards, recovery cards, onboarding, public demos, and issue triage. Use when work mentions AIppocampus UX, foreground surfaces, source-backed continuity usability, Linear/Raycast/Stripe-style clarity/speed/integration/recoverability, or when generic visual critique is too broad for AIppocampus product surfaces.
| name | AIppocampus |
| description | Use AIppocampus source-backed continuity through the repo MCP and CLI surfaces. |
| disable-model-invocation | true |
Use this when the user asks Claude Code to recall project context, check AIppocampus memory health, or prepare explicit Claude Code transcript onboarding.
AIppocampus is source-backed continuity. Do not claim model-native memory, innate recall, or private transcript access. Treat summaries as navigation layers; when answering from memory, prefer source ids, source refs, and clean-source evidence over unsupported paraphrase.
Aim for one source-backed recall moment before diagnostics. If source is already registered, search or ask for a bounded agent route:
aippocampus search "a distinctive old phrase" --cwd "$PWD"
aippocampus agent recall "old decision or handoff cue" --json
aippocampus agent deepen --request 1 --last-recall --json
Treat search hits, recall routes, and AIppo/self-note packets as navigation until source is reopened for exact, stale, sensitive, disputed, or high-risk claims.
Preview Claude Code transcript registration before writing anything:
aippocampus onboard --provider claude-code --dry-run --format json
Only run the write form after the user explicitly asks to register Claude Code history:
aippocampus onboard --provider claude-code --format json
After registration, return to the first success path and search for one source-backed snippet.
Use these checks when the first success path is blocked, or when the task is specifically host/MCP verification:
aippocampus health --cwd "$PWD"
aippocampus onboard --status --provider auto --cwd "$PWD"
aippocampus mcp status
aippocampus mcp list-tools --json
python tools/aippocampus/smoke/smoke_claude_code_mcp_host.py --json
If the MCP host is configured and the user wants a live proof, use the opt-in tool-call smoke:
python tools/aippocampus/smoke/smoke_claude_code_mcp_host.py --json --call-tool --cwd "$PWD" --max-budget-usd 0.20
Do not install/uninstall hooks, mutate Claude Code settings, or ingest private host history from this skill unless the user explicitly approves that exact action.
AIppocampus provides Claude Code hook status/dry-run/install/uninstall/smoke
commands for the scoped UserPromptSubmit and Stop contract:
aippocampus hooks claude-code status --json
aippocampus hooks claude-code dry-run --json
aippocampus hooks claude-code install --json
aippocampus hooks claude-code uninstall --json
aippocampus hooks claude-code smoke --json
status, dry-run, and smoke do not mutate Claude Code settings. install
and uninstall mutate only AIppocampus-owned Claude Code handler entries after
explicit operator command. aippocampus hooks prompt and aippocampus hooks lifecycle remain Codex-only installer/status tools, so using
--provider claude-code for onboarding does not install Claude Code host hooks.