Update to Eggshell

{
  "description": "Set up, inspect, or troubleshoot Eggshell local memory for Codex. Use when the user asks to install Eggshell, inspect a handoff or pending turn, change memory settings, or diagnose missing cross-chat memory. Ordinary coding tasks use the automatic hooks without loading this skill.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 214
    }
  ],
  "name": "eggshell",
  "skill_md_contents": "---\nname: eggshell\ndescription: Set up, inspect, or troubleshoot Eggshell local memory for Codex. Use when the user asks to install Eggshell, inspect a handoff or pending turn, change memory settings, or diagnose missing cross-chat memory. Ordinary coding tasks use the automatic hooks without loading this skill.\n---\n\n# Eggshell\n\nEggshell records work and observed outcomes locally. Hooks select relevant\nhistory for later Codex chats. Use this skill for setup and memory controls;\nnormal tasks do not need model-authored summaries or manual memory maintenance.\n\n## Setup\n\n1. Check macOS/Linux, ARM64/x86-64, Python 3, and Codex command-hook support.\n   Resolve this skill's installed path: the plugin root is two levels above\n   this `SKILL.md` directory. Use absolute paths for the bundled helpers.\n2. Explain that setup downloads a checksummed Eggshell runtime, Python packages,\n   and MiniLM. The default install root is `~/.local`; preserve an existing\n   `EGGSHELL_PREFIX`. Once setup is authorized, run `python3 <plugin-root>/scripts/setup.py`.\n   This installs only the runtime. Do not run the standalone release installer\n   after directory installation; it registers another copy of the hooks.\n3. Check `codex plugin list --marketplace eggshell --json` for the older standalone\n   installation. If migrating that installation, remove only `eggshell@eggshell`\n   with `codex plugin remove eggshell@eggshell --json` before enabling directory\n   hooks. Keep the runtime and `.egg` files. Do not remove unrelated plugins.\n4. In the intended project, check for `.eggshell.toml`. If absent, run\n   `<prefix>/bin/egg init`; if present, inspect it and retain the user's settings.\n   Add `<prefix>/bin` to the relevant PATH. Custom prefixes must also be present\n   in Codex's environment as `EGGSHELL_PREFIX`.\n5. Have the user review and enable Eggshell's hooks through `/hooks`, then start\n   a new chat. Verify memory with an actual related two-chat example: complete\n   an investigation, run `!egg keep`, ask a related question in a separate chat\n   in the same project, and inspect `!egg graph`. Installation alone does not\n   prove that a handoff was received.\n\n## Inspect and control memory\n\nRun `<plugin-root>/bin/egg` with the current thread environment. The equivalent\nuser shell commands inside Codex are:\n\n- `!egg`: settings and staged turn.\n- `!egg inspect`: resolved files and stored-state identifiers.\n- `!egg graph`: the handoff actually delivered, without rerunning retrieval.\n- `!egg why`: selection details.\n- `!egg diff`: preview the staged turn before saving.\n- `!egg keep`: explicitly save a finished turn (normal saving is automatic).\n- `!egg drop`: clear the active turn; saved observations and queued commits remain.\n- `!egg next private`: read memory without saving the next turn.\n- `!egg next off`: disable recording and context for the next turn.\n- `!egg off` / `!egg on`: disable or enable memory for the current chat.\n\nDo not keep, discard, or change settings merely because the user asks to inspect\nmemory. Read-only mode still sends selected prior work to Codex. Work files can\ncontain prompts, code, and tool output; do not publish their contents as part of\na support report without authorization.\n\n## Troubleshooting\n\nFor missing context, check hook enablement, the active profile and paths, whether\nthe earlier observations reached the selected `.egg`, and whether the new request\nrelates to that work. Tool results are saved during the turn; the final answer is\nqueued at Stop. A failed write stays queued and retries independently of hooks.\nDo not recommend repeating an investigation merely because a hook timed out.\nA new chat in another checkout may have a different work file. An empty handoff\nis possible when no relevant work is found.\n\nFor setup failures, use the actual error. A checksum mismatch must stop setup;\ndo not bypass verification. Hooks perform no dependency downloads. Missing\nruntime leaves Codex usable but provides no Eggshell memory. A failed search\nprovider permits ordinary matching; it does not establish successful semantic\nsearch. See the public guide for custom configurations and recovery:\nhttps://github.com/momonpya/eggshell/blob/main/docs/codex-plugin.md\n\nTreat old outcomes as evidence, including failures and timeouts. Distinguish\nreused findings from new checks and explicitly unverified facts. This skill does\nnot make memory evidence current or establish a new token-saving measurement.\n"
}