docs

Skills & Commands

Skills

cortex-broadcast auto

Trigger: After a Raw has been distilled, to fuse it into related existing pages ("broadcast", "compound this into the vault"), or auto-dispatched at the end of the distill flow.

llm-wiki style broadcast ingest — conversational update of related existing pages when a Raw has been distilled. Use when the user says "broadcast", "跑 broadcast", "compound this into the vault", "merge pending-merge", "process broadcast queue", or when cortex-distill invokes broadcast inline after Step 8 commit (automatic dispatch for every new / pending-merge Raw).

broadcastprocess broadcast queue

cortex-distill auto

Trigger: When the user wants to distill Raw session records into Notes/Projects ("提煉", "整理 raw", "distill").

Distill raw session records into refined Notes and Projects. Use when the user says "提煉", "整理 raw", "distill", or "distill raw records".

distill this week's rawdistill raw records

cortex-evolve auto

Trigger: When the user wants to save knowledge to the vault ("存到 cortex", "記一下"), or when the session-suggest hook recommends saving.

Save knowledge to the cortex vault. Use when the user says "存到 cortex", "記一下", "save to cortex", "記到筆記", "cortex evolve", or when the session-suggest hook recommends saving content. Handles Notes and Projects.

save to cortexnote this decision downremember this

cortex-query auto

Trigger: When the user explicitly asks to search the vault ("查 cortex", "之前有記過", "/cortexes:query"), or when using-cortex routes a request here after one of its four signals. Not for general or merely difficult questions.

Search and retrieve content from the cortexes vault — the user's external memory. Use when the user explicitly asks to search or recall the vault ("查 cortex", "之前有記過", "cortex 裡有沒有", "check my notes", "what did I write about", `/cortexes:query`), or when the using-cortex skill routes a request here after one of its four prior-context signals. Do not use for general questions, for fresh work with no prior-context signal, because a question is merely hard or technical, or after the user has opted out of the vault.

check cortex for nginx noteshave I written about this beforewhat did I write about cortex-vec

cortex-takeoff auto

Trigger: When context is running low and work needs to hand off to a later session ("交接", "takeoff", "交棒"). Produces temporary hand-off batons — one per work line — that are never committed or indexed.

Create or resume a session takeoff baton — a curated, ephemeral, git-ignored hand-off note that lets the next Claude session continue a long-running task. A repo can hold several batons at once, one per work line (topic). Use when the user says "交接", "takeoff", "交棒", "context 快滿了交接給下個 session", "hand off to next session", "/cortexes:takeoff", "takeoff resume", or "takeoff done". The baton is scaffolding, not knowledge: it is never committed, distilled, broadcast, or indexed.

hand off to the next sessiontakeoff resumetakeoff done

using-cortex auto

Trigger: Four signals only — an explicit request, a reference to earlier work ("上次的", "之前那個", "we discussed"), a topic SessionStart actually listed, or resuming a session. Routes those to cortex-query, answers directly otherwise, and stays off once the user picks "直接開始工作".

Use when the user asks to check the cortex vault, refers to earlier work ("last time", "that project", "we discussed", "之前那個", "上次的"), asks to resume something from a previous session, or names a topic the SessionStart hook listed for this vault. Routes the request to the cortex-query skill so the answer is grounded in the user's own notes instead of re-derived. Do not use for general questions, for fresh work with no prior-context signal, or when the user has asked to skip the vault.

上次那個 nginx 的問題後來怎麼解的continue where we left offwe discussed this last week — what did we decide

Commands

/cortexes:broadcast

Run broadcast on a distilled Raw — update related existing pages conversationally

/cortexes:broadcast --list

/cortexes:distill

Distill raw session records into refined Notes and Projects

/cortexes:distill this week/cortexes:distill 2026-06-30

/cortexes:evolve

Save knowledge to the cortex vault (Notes or Projects) and update index

/cortexes:evolve

/cortexes:genesis

Initialize cortex vault — set up config, vault structure, and rebuild index

/cortexes:genesis /srv/cortex/cortexes:genesis ~/cortex

/cortexes:query

Manually search the cortex vault (Notes, Projects, Raw) for existing notes

/cortexes:query nginx 憑證更新/cortexes:query what did I decide about the vector store

/cortexes:takeoff

Create, resume, or clear a session hand-off baton (one per work line)

/cortexes:takeoff vec-index-rebuild/cortexes:takeoff resume/cortexes:takeoff done vec-index-rebuild

Hooks

  • SessionEnd — Auto-generates a full report (commits, findings, decisions) and saves it to the vault's Raw/ on session end — the entry point for automatic capture. It also reclaims redundant snapshots, so one conversation stays one Raw across /clear and --resume.
  • SessionStart — Detects the current repo and injects the vault's topic names plus a short menu — metadata and an offer, not note contents. Loading anything is opt-in; option 1 runs the search, while "直接開始工作" prevents subsequent content loading and proactive searches for that session.

Tips

  • Retrieval is deliberately narrow — it fires on four signals, not on every hard question. When you do want the vault consulted, say so or run /cortexes:query; that always counts.
  • distill automatically dispatches broadcast afterward to fuse new knowledge into existing pages; no need to run it manually.
  • The vault is the source of truth (markdown + git); the vector store can always be rebuilt with /cortexes:genesis.
  • Legacy phrasing still works — "存到 cortex", "查 cortex" and friends keep triggering the skills after the 2.0.0 rename to Cortexes; only the slash-command prefix moved.

Watch out

  • The takeoff baton is temporary scaffolding — it is never committed, distilled, broadcast, or indexed. Don't rely on it as the only place long-term knowledge lives.
  • Without OPENAI_API_KEY, cortex-vec drops the embedding stream and searches its local BM25 index instead — still real retrieval, just lexical. The CLI itself is the hard requirement; install it with uv or pip.
  • Picking "直接開始工作" at session start suppresses proactive lookup for the rest of that session by design. Ask explicitly, or run /cortexes:query, to search anyway.