mycodebug-capturelisted

Use this skill when a Myco session, prompt, tool use, or attachment appears to have gone missing — the agent says "I sent that" but it isn't in the dashboard, a session shows zero batches, MCP tool calls hang or silently no-op, hooks aren't firing in a worktree, the buffer file isn't growing, FK constraint errors appear in the daemon log, or the symptom is "capture went silent." Also use when investigating any reported capture regression in the Myco repo. Walks the capture lifecycle top-down — agent → hook → daemon HTTP → buffer → registry → SQLite → transcript miner — and tells you which layer to look at, in what order, with the exact command to run. Replaces the "investigate capture loss from scratch" antipattern that produced repeated one-off patches.
goondocks-co/myco · ★ 13 · AI & Automation · score 79

Install: claude install-skill goondocks-co/myco

# Debug Capture Top-down procedure for "why didn't this land in Myco?" Walks the capture lifecycle in order. The first layer whose check fails is the layer the bug lives in. Stop investigating once that layer is identified; do not assume two layers are simultaneously broken. ## Why this exists Several independent capture regressions all presented identically — "session went silent" — and each was investigated from scratch via process trees, buffer mtimes, and intuition. The pattern wasted hours. This skill replaces intuition with a procedure that starts at the same step every time. ## Background reading Skim once before first use; refer back as needed: - **`references/capture-lifecycle.md`** — the layered tenet: what each layer is, what's authoritative at it, what its failure looks like from above. - **`references/symbiont-capture-contract.md`** — per-agent matrix: hook events, session ID hook field, transcript path convention, project root resolution. ## Inputs You need: - A **session_id** that's suspected to be under-captured. - The **vault dir** the agent is using. Typically `<repo-root>/.myco`. In a worktree it walks up to the main repo's `.myco`. - The **Grove database path**. Typically `~/.myco/groves/<grove-id>/myco.db`. Find it with `myco grove list` if unsure. - The **agent's transcript path**, if available. The hook payload at Stop carries this; otherwise infer per `references/symbiont-capture-contract.md`. ## Procedure ### Step 1 — Did the hook fire? ``