← ClaudeAtlas

cortex-broadcastlisted

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).
XBlueSky/cortexes · ★ 20 · AI & Automation · score 79
Install: claude install-skill XBlueSky/cortexes
# Cortex Broadcast — Compounding Ingest Propagate insights from a distilled Raw into related existing Notes/Projects pages through conversational per-page edits. ## Resolve Vault Path and Config Read `~/.cortex/config.json`: ```bash jq -r '.vault_path' ~/.cortex/config.json jq -r '.broadcast.target_top_n // 5' ~/.cortex/config.json jq -r '.broadcast.target_min_score // 0.40' ~/.cortex/config.json ``` If the config file doesn't exist, tell the user to run `/cortexes:genesis` first. ## Step 1: Resolve Arguments The command supports three invocations: | Form | Action | |------|--------| | `/cortexes:broadcast` (no args) | Pop the first (oldest) Raw from the eligible queue | | `/cortexes:broadcast <raw-path>` | Use the specified Raw (relative or absolute path) | | `/cortexes:broadcast --list` | Print the eligible queue and exit | ## Step 2: Build Eligible Queue A Raw is eligible iff its marker meets **all** of: - Contains `<!-- distilled: YYYY-MM-DD → ... -->` (Phase 1 processed). - Outcome is `new` or `pending-merge` (the marker content after `→` is either a path like `Notes/X.md` / `Projects/Y/Z.md`, **or** starts with `pending-merge:`; anything else — `(skip: routine)`, `(no insight)`, or the pre-Phase-1 legacy `(no extractable content)` — is ineligible). - Does not already contain any of: `| broadcast:`, `| merged:`, `| no-broadcast:`. Build the list via: ```bash cortex-vec broadcast-queue --root <vault>/Raw ``` This applies the three criteria above agai