一键导入
ctx-note
Capture a personal observation, written note, or voice memo into project context. Synthesises and validates the note, links to a person if relevant.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Capture a personal observation, written note, or voice memo into project context. Synthesises and validates the note, links to a person if relevant.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Point at a folder of markdown and write one reconciled, provenance-tagged, staleness-aware current-state.md sidecar — the summary-of-summaries that updates and self-corrects across runs. Works on any markdown corpus (call summaries, transcripts, notes, PRDs); imposes no folder structure and edits nothing but its own output file. Use when the user runs /synthesise, asks for a current state / synthesis / "what do we know now" over a folder, or wants a folder's scattered markdown reconciled into one living state file.
Add a new item to any portfolio project. Reads the portfolio's CLAUDE.md for item name and template path. Creates the item folder from templates/item/, updates TRACKER.md. Works for any portfolio type (opportunities, ideas, articles, etc.).
Load project context and start a session with a compact briefing of recent work and next steps
Add context to the active project. Triages the input as a meeting transcript, document, personal note, or chat thread — then routes to the right writer. Replaces the four `/ctx-*` entry points.
Capture a WhatsApp, Slack, or DM thread into project context. Handles multi-party threads with deduplication — import the same thread repeatedly and only new messages get processed.
Add a document to the project and update synthesised context. Run this whenever new source material arrives — calls, transcripts, documents, briefs. Walks through adding frontmatter, updating context files, and syncing people records.
| name | ctx-note |
| description | Capture a personal observation, written note, or voice memo into project context. Synthesises and validates the note, links to a person if relevant. |
| user_invocable | true |
Two phases:
Step 1 — Print:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CAPTURE A NOTE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Then print these one-line tips (non-blocking — proceed to Step 2 without waiting):
Tip: make sure auto-accept edits is ON (Shift + Tab) — background synthesis fails silently otherwise.
Tip: /add-context auto-detects type — you can route through it next time instead of /ctx-note.
Step 2 — Project. Read [workspace-root]/.current-session for the active project. Show pre-selected, list others. Wait for confirmation.
Step 3 — Content. Ask: Paste note below, or give a file path:
Step 4 — Person (optional). Ask: Is this about a specific person? (name, or "none" to skip)
If yes, match to [PROJECT_ROOT]/people/. If no match found, offer to create a stub.
Step 5 — Context (optional). Ask: Any context? e.g. post-event reflection, follow-up to April 16 (type "none" to skip):
Step 6 — Date. Check content for a date. If found, confirm. If not: Date (e.g. 17 Apr 2026):
Step 7 — Slug. Generate a short slug from the content topic (e.g. april-16-reflection). Show and ask to confirm or edit.
Show summary:
Project: [name]
About: [person name / "Not linked"]
Context: [context / "None"]
Date: [date]
Folder: notes/[DATE]-[slug]/
Ask: Looks right? [Y/N]
Say: Got it. Processing in the background — you can keep working.
Spawn background agent (run_in_background: true). Pass:
PROJECT_ROOTCONTENT_PATH — file path if given; if pasted, write verbatim to a temp path and pass thatABOUT_PERSON — person slug if linked, else nullCONTEXT — optional context stringDATE — e.g. "2026-04-17"NOTE_FOLDER — [PROJECT_ROOT]/intelligence/notes/[DATE]-[slug]/Tell the agent: Read .claude/skills/ctx-note/BACKGROUND.md for processing instructions. Do not ask questions — proceed through all steps.
[PROJECT_ROOT]/intelligence/notes/
[DATE]-[slug]/
raw.md
synthesis.md
validation.md