" <bodyfile> --kind <kind> [--aliases a,b] [--tags t1,t2] [--source p1,p2] python3 "$CHORUS" capture "<title>" --inbox # unknown home -> idempotent inbox line ``` **If capture exits `76` (duplicate gate):** the title strongly resembles an existing entity — do NOT retry blindly. Show the operator the printed candidates and either update the existing note (`capture ... --merge-into <slug>`) or, only after they confirm it's genuinely distinct, re-run with `--force`. Drop to the low-level verbs only for shapes `capture` doesn't model (a project `## Status` replace, an ADR mirror, a daily-note edit): ```bash python3 "$CHORUS" put <routed/path>.md <bodyfile> # create/overwrite (verifies) python3 "$CHORUS" patch <path>.md append heading "<H1::Sub>" <bodyfile> # targeted append ``` Write in third person about the vault owner; never put `[[wikilinks]]` in frontmatter. `capture` handles `agent_written`, `source_notes`, indexing, and linking for you; if you write by hand, `resolve "<title>"` first to avoid duplicates and `bump` `updated:` only on substantive changes.

--- description: Save to CHORUS memory — route content to its canonical home (search-first, idempotent) argument-hint: "[what to remember]" --- Use the **chorus-memory** skill to persist this to the CHORUS vault: > $ARGUMENTS Prefer the one-call **`capture`** — it routes (via the entity index), derives the canonical path, stamps complete frontmatter (kind-default `status`, the kind seeded into `tags`), indexes, auto-links mentioned entities, and writes the Agent-Log line. Pick the `--kind` from the content (`person, company, concept, reference, meeting, project, area, semantic, episodic, working, skill, decision`); add `--tags` when obvious; use `--inbox` only when the home is genuinely unknown. Write multi-line bodies to a file with the Write tool (cross-platform, no heredoc) — updates to an existing entity preserve the whole body, so don't pre-trim it. ```bash CHORUS="${CLAUDE_PLUGIN_ROOT}/skills/chorus-memory/scripts/chorus.py" # run with: python3 "$CHORUS" ... (Windows: python / py -3) [ -f "$CHORUS" ] || CHORUS=$(ls /sessions/*/mnt/.remote-plugins/*/skills/chorus-memory/scripts/chorus.py 2>/dev/null | head -1) # CoWork sandbox fallback python3 "$CHORUS" capture "" <bodyfile> --kind <kind> [--aliases a,b] [--tags t1,t2] [--source p1,p2] python3 "$CHORUS" capture "<title>" --inbox # unknown home -> idempotent inbox line ``` **If capture exits `76` (duplicate gate):** the title strongly resembles an existing entity — do NOT retry blindly. Show the operator the printed candidates and either update the existing note (`capture ... --merge-into <slug>`) or, only after they confirm it's genuinely distinct, re-run with `--force`. Drop to the low-level verbs only for shapes `capture` doesn't model (a project `## Status` replace, an ADR mirror, a daily-note edit): ```bash python3 "$CHORUS" put <routed/path>.md <bodyfile> # create/overwrite (verifies) python3 "$CHORUS" patch <path>.md append heading "<H1::Sub>" <bodyfile> # targeted append ``` Write in third person about the vault owner; never put `[[wikilinks]]` in frontmatter. `capture` handles `agent_written`, `source_notes`, indexing, and linking for you; if you write by hand, `resolve "<title>"` first to avoid duplicates and `bump` `updated:` only on substantive changes.