메뉴
Store a document, email, or text for future reference with entity linking and provenance. See also: `ingest-sources` for multiple files; `capture-meeting` if it's meeting notes; `summarize-doc` to get a summary without filing.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | file-document |
| description | Store a document, email, or text for future reference with entity linking and provenance. See also: `ingest-sources` for multiple files; `capture-meeting` if it's meeting notes; `summarize-doc` to get a summary without filing. |
Store any document, email, or text for future reference with proper entity linking and provenance tracking.
/file-document or natural language:
This command is for ad-hoc document capture. Use it when:
Note: For meeting transcripts specifically, use /capture-meeting which includes extraction.
Ask if not obvious:
Determine:
├── source_type: gmail, transcript, upload, capture
├── filename: YYYY-MM-DD-[entity]-[topic].md
├── about: [list of entity names mentioned]
└── summary: One-line description
claudia memory document store \
--filename "Descriptive name" \
--source-type "gmail|transcript|upload|capture" \
--summary "Brief description" \
--about "entity1,entity2" \
--project-dir "$PWD" \
< content.md
(Pipe the FULL raw text via stdin; never summarize)
**Filed**
**File:** [filename]
**Location:** [storage path]
**Linked to:** [entity names]
**Summary:** [one-line summary]
The document is now searchable and linked to [entities].
You can find it later with:
- "Show me documents about [entity]"
- "Find the email from [person]"
- claudia memory document search --entity "[name]" --project-dir "$PWD"
| Type | Use When | Example |
|---|---|---|
gmail | Email content | "Here's an email from Sarah..." |
transcript | Meeting notes/recordings | "Notes from today's call..." |
upload | PDFs, contracts, formal docs | "Here's the contract..." |
capture | Research, web content, misc | "I found this article..." |
Documents are automatically routed to entity-aware folders:
If about a person:
people/sarah-chen/emails/2026-02-04-proposal.md
people/sarah-chen/documents/2026-02-04-contract.pdf
If about an organization:
clients/acme-corp/emails/2026-02-04-partnership.md
If about a project:
projects/rebrand/documents/2026-02-04-brief.md
If no entity linked:
general/documents/2026-02-04-misc.md
User: "Here's an email from Jim about the partnership terms. Save it."
claudia memory document store \
--filename "2026-02-04-jim-ferry-partnership.md" \
--source-type "gmail" \
--summary "Jim Ferry re: partnership terms and next steps" \
--about "Jim Ferry" \
--project-dir "$PWD" < email.md
Response:
"Filed Jim's email about partnership terms.
Saved to: people/jim-ferry/emails/2026-02-04-partnership.md
You can find it later by asking about Jim's documents."
User: "Here's some info I found about competitor pricing. Keep this."
claudia memory document store \
--filename "2026-02-04-competitor-pricing-research.md" \
--source-type "capture" \
--summary "Competitor pricing analysis notes" \
--project-dir "$PWD" < research.md
Response:
"Filed your competitor pricing research.
Saved to: general/documents/2026-02-04-competitor-pricing-research.md"
User: "Save this contract from Acme Corp"
claudia memory document store \
--filename "2026-02-04-acme-corp-contract.md" \
--source-type "upload" \
--summary "Service agreement with Acme Corp" \
--about "Acme Corp" \
--project-dir "$PWD" < contract.md
Response:
"Filed the Acme Corp contract.
Saved to: clients/acme-corp/documents/2026-02-04-contract.md"
If you also extract facts from the document:
claudia memory save or claudia memory batchclaudia memory document store --memory-ids "id1,id2,..." to link provenanceThis creates the chain: memory -> document -> file on disk.
Iteratively improve a local artifact (draft, document, page) by running a hill-climbing loop. The user names the artifact, the evaluator, and the budget. Claudia edits the artifact, scores it, keeps it if better or reverts if worse, repeats. Use when user says "iterate on this", "loop on this until it's better", "run experiments on this draft", "auto-research this", "make this better and don't stop until it's good". Workspace-scoped, never touches live files, no external actions during the loop.
Propose a personalized team of specialized agents based on the user's profile, goals, and how they actually work. Runs the proposal through an independent Checker, gates on the user's approval, and applies with rollback. Use when the user says "build my team", "set up my agents", "what agents should I have", "design my team", "/build-team", or asks Claudia to tailor her team to their work. See also: `hire-agent` for proactive single-agent suggestions; `structure-generator` for folder scaffolding; `capability-suggester` for command-level additions.
End-of-session reflection generating persistent learnings about user preferences, communication patterns, and cross-session insights. Activates when wrapping up a session, or when user says "let's wrap up", "end the session", "time to reflect", or "meditate". Also extracts judgment rules from decisions made during the session. See also: `weekly-review` and `growth-check` for time-based reflection cadences.
Launch the Brain Monitor TUI, a real-time terminal dashboard for watching Claudia's memory system. Triggers on "brain monitor", "show dashboard", "memory dashboard", "terminal brain". See also: `brain` for a 3D graph view in the browser.
Launch the Brain Visualizer, a real-time 3D view of memory and relationships. Triggers on "show your brain", "visualize memory", "open the brain", "memory graph". See also: `brain-monitor` for a terminal dashboard alternative.
Process meeting notes or transcript to extract decisions, commitments, and insights. Use when user shares transcript or says "capture this meeting", "here are my notes from the call". See also: `meeting-prep` for pre-call briefings; `follow-up-draft` for post-meeting emails.