recalllisted

# Recall Retrieve relevant history from session reports, compiled artifacts, and proposals by keyword search. **Not `/hermit-brain`** — that synthesizes a snapshot of the hermit's current state (fragile zones, stale proposals, recent learnings). **Not `/knowledge`** — that lints knowledge directory structure for stale or missing-type artifacts. This skill does full-text retrieval: you give it a query, it returns matching history with `file:line` snippets. ## Step 0 — Channel reply If this skill was invoked from a channel-arrived message (the inbound prompt contains a `<channel source="...">` tag), deliver the response via that channel's reply tool. Otherwise emit to conversation. ## Step 1 — Run search Extract the search query from the operator's message — the topic or phrase after "recall", "what did I learn about", "when did we last touch", "what did we decide about", or similar phrasing. Then run: ```bash node ${CLAUDE_PLUGIN_ROOT}/scripts/search.js .claude-code-hermit "<query>" ``` The query is untrusted operator/channel input. Pass it as a single literal argument: strip any double quotes, backticks, `$`, `;`, and `|` from the extracted query before substituting it into the command so it cannot terminate the quoted string or chain a second command. Optional filters (append to the command as needed): - `--type=<type>` — restrict to a specific artifact type (e.g. `review`, `briefing`) - `--since=<YYYY-MM-DD>` — exclude files older than this date - `--limit=<n>` — c