Claude-skill-registry brain-dump-assistant
Manage a personal knowledge capture system. Use when the user wants to capture ideas, track todos, organize projects, review their brain dump, or mentions "brain dump", "capture this", "add to my list", "what's on my plate", "what should I focus on", or "daily review".
git clone https://github.com/majiayu000/claude-skill-registry
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/brain-dump-assistant" ~/.claude/skills/majiayu000-claude-skill-registry-brain-dump-assistant && rm -rf "$T"
skills/data/brain-dump-assistant/SKILL.mdBrain Dump Assistant
A CLI for externalizing your working memory - capture ideas, projects, features, todos, and questions without the overhead of complex tools.
Why?
Your brain is for having ideas, not holding them. But sticky notes get lost, notepads pile up unread, and tools like Asana are overkill for personal capture.
brain-dump solves this by providing:
- Zero-friction capture - dump thoughts in seconds
- Structured retrieval - find anything with search and filters
- AI-assisted triage - agents help you organize, prioritize, and act
Agent Mindset
When assisting users with their brain dump:
-
Capture first, organize later - Never block on classification during fast capture. Get the thought out, refine later.
-
Proactive triage - Regularly surface raw entries needing processing. Don't let the inbox grow stale.
-
Connect the dots - Link related entries, identify patterns, consolidate ideas into projects.
-
Reduce cognitive load - Present summaries and prioritized lists, not exhaustive dumps.
-
Preserve context - Include enough detail for future recall. A cryptic note is useless later.
-
Respect simplicity - Simple thoughts don't need tags, priorities, and parents. Don't over-engineer.
Operating Modes
Detect user intent and respond appropriately:
| Mode | Triggers | Behavior |
|---|---|---|
| Capture | "Add this...", "Remind me...", "I had an idea..." | Fast capture, minimal questions, default to idea type |
| Review | "What's on my plate?", "Daily review", "Show me..." | Stats + prioritized summary, grouped by type |
| Triage | "Process my brain dump", "What needs attention?" | Surface raw entries, help classify and prioritize |
| Focus | "What should I work on?", "Priority items" | P1 todos + active projects, clear next actions |
| Cleanup | "Archive completed", "Clean up old stuff" | Bulk operations with preview and confirmation |
Quick Start
| Task | Command |
|---|---|
| Capture idea | |
| Add todo | |
| Add question | |
| List active | |
| See all | |
| Search | |
| Show details | |
| Mark done | |
| Get stats | |
Pre-flight Check
Before operations, verify the tool is ready:
brain --version # Verify installed brain stats # Quick health check
If
brain: command not found, the user needs to install: npm install -g brain-dump
Command Reference
Capture Commands
brain add <content>
brain add <content>Quick capture of a thought.
brain add "What if we used a graph database?" brain add "Need to review the API design" --type todo --priority 1 brain add "Meeting notes from standup" --type note --tags "meetings,weekly" brain add --type project --title "Website Redesign" "Complete overhaul of the marketing site..."
Options:
: idea, project, feature, todo, question, reference, note (default: idea)--type <type>
: Short title (auto-extracted from first line if not provided)--title <title>
: 1=high, 2=medium, 3=low--priority <1|2|3>
: Comma-separated tags--tags <tags>
: Parent entry ID--parent <id>
: JSON output--json
brain todo <content>
brain todo <content>Shorthand for adding a todo.
brain todo "Review PR #42" # Equivalent to: brain add "Review PR #42" --type todo
brain question <content>
brain question <content>Shorthand for adding a question.
brain question "Should we migrate to TypeScript?" # Equivalent to: brain add "..." --type question
Query Commands
brain list
brain listList entries with filtering.
brain list # Active + raw (default) brain list --all # All except archived brain list --type todo # Only todos brain list --status raw # Needs triage brain list --priority 1 # High priority only brain list --tags work,urgent # Has ALL specified tags brain list --since 7d # Created in last 7 days brain list --json # JSON output for parsing
Options:
: Filter by entry type--type <type>
: raw, active, someday, done, archived (default: raw,active)--status <status>
: Comma-separated, AND logic--tags <tags>
: Filter by priority--priority <1|2|3>
: Children of specific entry--parent <id>
: Only entries without parent--orphans
: e.g., 7d, 24h, 2w--since <duration>
: All statuses except archived--all
: Include done entries--done
: Show only archived--archived
: Max entries (default: 50)--limit <n>
: created, updated, priority--sort <field>
: Reverse sort order--reverse
: JSON output--json
brain show <id>
brain show <id>Show full entry details.
brain show a1b2c3d4 brain show a1b2c3d4 --with-children brain show a1b2c3d4 --with-related brain show a1b2c3d4 --json
brain search <query>
brain search <query>Full-text search across content and titles.
brain search "database" brain search "meeting" --type note --since 30d brain search "API" --json
Modify Commands
brain edit <id>
brain edit <id>Edit entry content.
brain edit a1b2c3d4 # Opens $EDITOR brain edit a1b2c3d4 --content "New text" # Non-interactive brain edit a1b2c3d4 --append "Follow-up" # Add to existing brain edit a1b2c3d4 --title "New title"
brain set <id>
brain set <id>Update entry metadata.
brain set a1b2c3d4 --type project brain set a1b2c3d4 --status active brain set a1b2c3d4 --priority 1 brain set a1b2c3d4 --tags "work,Q1" brain set a1b2c3d4 --add-tags "important" brain set a1b2c3d4 --remove-tags "draft" brain set a1b2c3d4 --clear-priority brain set a1b2c3d4 --parent b2c3d4e5
brain link <id1> <id2>
brain link <id1> <id2>Create relationships between entries.
brain link a1b2c3d4 b2c3d4e5 # Add to related brain link a1b2c3d4 b2c3d4e5 --as-parent # Set hierarchy brain link a1b2c3d4 b2c3d4e5 --unlink # Remove relationship
Bulk Commands
brain done <ids...>
brain done <ids...>Mark entries as done.
brain done a1b2c3d4 brain done a1b2c3d4 b2c3d4e5 c3d4e5f6 # Multiple brain done --type todo --tags "sprint-1" # By filter brain done --dry-run --type todo # Preview first
brain archive <ids...>
brain archive <ids...>Archive entries (hides from default view).
brain archive a1b2c3d4 brain archive --status done --since 30d # Old completed items brain archive --dry-run --status done # Preview
brain delete <ids...>
brain delete <ids...>Delete entries (logged for undo).
brain delete a1b2c3d4 brain delete a1b2c3d4 b2c3d4e5 --confirm brain delete --status archived --since 90d # Permanent cleanup brain delete --dry-run --type reference # Preview
Safety:
- All deletions logged to enable restore
-
10 entries requires
or--confirm--force - Entries with children require
--force
brain restore
brain restoreRestore deleted entries.
brain restore --last 1 # Most recent brain restore --last 5 # Last 5 brain restore --ids a1b2c3d4,b2c3d4e5 # Specific IDs brain restore --list # Show deletion log
Maintenance Commands
brain stats
brain statsOverview statistics.
brain stats brain stats --json
brain export
brain exportExport entries.
brain export # All to stdout brain export --file backup.json # To file brain export --type todo --status active # Filtered
brain import <file>
brain import <file>Import entries.
brain import backup.json brain import backup.json --dry-run brain import backup.json --merge # Update existing + add new brain import backup.json --skip-existing # Only add new
Workflow Patterns
Daily Review
Run this each morning to get oriented:
- Health check:
brain stats - Triage raw entries:
brain list --status raw - Focus list:
brain list --priority 1 --type todo - Help user decide what to work on first
Weekly Review
Run this weekly to maintain hygiene:
- Celebrate:
- show what was accomplishedbrain list --done --since 7d - Check stalled:
- find items not touchedbrain list --status active --sort updated - Review projects:
- are they progressing?brain list --type project - Clean up:
- archive completed itemsbrain archive --status done --since 7d
Triage Workflow
When user has many raw entries:
- Fetch:
brain list --status raw --json - For each entry, determine:
- Type (idea, todo, project, question, reference, note)
- Priority (1, 2, 3, or none)
- Tags (infer from content)
- Parent (if belongs to existing project/feature)
- Update:
brain set <id> --type todo --priority 1 --tags "work" - If entry is actually multiple items, split and re-capture
- Mark refined:
brain set <id> --status active
Capture Mode
When user is dumping thoughts rapidly:
- Just capture with
- don't interrupt for classificationbrain add "..." - Use default type (idea) and status (raw)
- After the brain dump session, offer to triage
Classification Rules
Type Detection Heuristics
| Indicator | Likely Type |
|---|---|
| Starts with action verb ("Build", "Write", "Fix", "Review") | |
| Contains "?" or seeking information | |
| Multi-step initiative, long-term scope | |
| Specific capability/enhancement within a project | |
| Link, quote, or factual information | |
| Observation with no clear action | |
| Speculative, "what if", creative | |
Priority Assignment
| Priority | Criteria |
|---|---|
| P1 (high) | Blocking other work, deadline within 48h, explicitly urgent |
| P2 (medium) | Important but not urgent, this-week scope |
| P3 (low) | Nice-to-have, someday-maybe, learning/exploration |
| None | Truly unprioritized, needs triage |
Safety Rules
Non-negotiable constraints:
- Never auto-delete - Always show what will be deleted and confirm
- Preserve context - Don't summarize away important details during capture
- Log before delete - All deletions are recoverable via
brain restore - Confirm bulk operations - Operations affecting >10 entries require confirmation
- Don't over-organize - Simple thoughts don't need tags, priorities, and parents
Two-Step Pattern for Bulk Operations
Critical for preventing accidental mass changes:
- Preview:
brain delete --status archived --since 90d --dry-run - Confirm: Show user what will be affected, get explicit approval
- Execute:
brain delete --ids "<specific-ids>" --confirm
Principle: Filters are for DISCOVERY, IDs are for EXECUTION.
Common Request Patterns
| User Says | Interpretation | Action |
|---|---|---|
| "Add this to my brain dump" | Fast capture | |
| "I need to remember to..." | Todo item | |
| "What's on my plate?" | Need overview | + |
| "What should I focus on?" | Need priorities | |
| "Process my brain dump" | Triage needed | Run triage workflow on raw entries |
| "This is done" / "I finished X" | Mark complete | |
| "Archive old stuff" | Cleanup | |
| "What did I do this week?" | Review completions | |
| "Find anything about X" | Search | |
| "Link these together" | Create relationship | |
Troubleshooting
| Problem | Solution |
|---|---|
| Run |
| Empty brain dump | Start with |
| Too many raw entries | Run triage workflow |
| Can't find entry | Use |
| Accidentally deleted | Use |
| Wrong type/status | Use |
Testing / Evaluation Scenarios
| Scenario | Expected Behavior | Failure Indicator |
|---|---|---|
| User says "capture this" | Immediate , no questions | Asking for type/priority during fast capture |
| User says "what's on my plate" | Stats + prioritized summary | Listing all 50 entries individually |
| User says "clean up" | Preview + confirmation | Auto-archiving without preview |
| Large deletion (>10 items) | Show count, ask confirmation | Proceeding without confirmation |
| User mentions deadline | Suggest P1 priority | Not detecting urgency |
| User's idea relates to existing project | Suggest linking | Not checking for related entries |
JSON Output Schemas
Entry Object
{ "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "content": "The full text of the entry", "title": "Short title (optional)", "type": "idea|project|feature|todo|question|reference|note", "status": "raw|active|someday|done|archived", "priority": 1|2|3|null, "tags": ["tag1", "tag2"], "parent": "parent-id|null", "related": ["id1", "id2"], "createdAt": "2026-01-05T08:30:00.000Z", "updatedAt": "2026-01-05T08:30:00.000Z", "source": "cli|agent|import" }
List Response
{ "success": true, "entries": [...], "total": 47, "returned": 12, "query": { "status": ["raw", "active"], "limit": 50 } }
Error Response
{ "success": false, "error": "Entry not found: a1b2c3d4", "code": "ENTRY_NOT_FOUND" }
Remember
- The goal is to externalize working memory, not build a perfect system
- Capture is king - never block a brain dump
- Structure serves retrieval, not organizational perfection
- The best system is one that gets used