para-second-brainOrganize your agent's knowledge using PARA (Projects, Areas, Resources, Archive) — then make it ALL searchable. The symlink trick enables full semantic search across your entire knowledge base, not just MEMORY.md. Includes session transcript indexing and memory flush protocol. Your agent finally has a real second brain.
Install via ClawdBot CLI:
clawdbot install halthelobster/para-second-brainYour agent's memory just got a massive upgrade. Full semantic search across your entire knowledge base — not just MEMORY.md.
Before v2.0: memory_search only found content in MEMORY.md and daily logs. Your entire notes/ folder was invisible to search. You had to manually know where to look.
After v2.0: One symlink command makes your entire PARA knowledge base searchable. Ask about anything in your notes — it finds it. Plus session transcripts and memory flush protocol to prevent context loss.
| Before | After |
|--------|-------|
| Search only MEMORY.md + daily logs | Search EVERYTHING |
| "I don't have that information" | Finds it instantly |
| Context compaction = lost information | Flush protocol saves critical context |
| Conversations forgotten | Session transcripts indexed |
Creates a "second brain" structure that separates:
There's another popular second-brain skill powered by Ensue. Both are great — they solve different problems:
| | PARA Second Brain (this skill) | Ensue Second Brain |
|---|---|---|
| Storage | Local files in your workspace | Cloud API (Ensue) |
| Cost | Free, self-hosted | Requires Ensue API key |
| Best for | Work context, agent continuity, project tracking | Evergreen knowledge base, semantic queries |
| Search | Clawdbot's memory_search | Ensue's vector search |
| Structure | PARA (Projects/Areas/Resources/Archive) | Namespaces (concepts/toolbox/patterns) |
| Use case | "What did we decide yesterday?" | "How does recursion work?" |
Use this skill if: You want file-based memory that works offline, costs nothing, and tracks ongoing work context.
Use Ensue's skill if: You want a cloud-hosted knowledge base optimized for semantic "what do I know about X" queries.
Use both if: You want PARA for work context + Ensue for evergreen knowledge. They complement each other.
workspace/
├── MEMORY.md # Curated long-term memory
├── memory/
│ └── YYYY-MM-DD.md # Daily raw logs
└── notes/
├── projects/ # Active work with end dates
├── areas/ # Ongoing life responsibilities
├── resources/ # Reference material
│ └── templates/ # Content templates
└── archive/ # Completed/inactive itemsRun this to scaffold:
mkdir -p memory notes/projects notes/areas notes/resources/templates notes/archiveBy default, memory_search only indexes MEMORY.md and memory/*.md. Your entire notes/ folder is invisible to semantic search!
Fix this with one command:
ln -s /path/to/your/workspace/notes /path/to/your/workspace/memory/notesExample:
ln -s /Users/yourname/clawd/notes /Users/yourname/clawd/memory/notesWhat this does: Creates a symbolic link so memory/notes/ points to your actual notes/ folder. Now Clawdbot's memory_search sees all your PARA notes.
Verify it worked:
ls -la memory/notes # Should show: memory/notes -> /path/to/notesTest the search:
Ask your agent something that's in your notes but NOT in MEMORY.md. If it finds it, the symlink is working.
Why this matters:
| Before | After |
|--------|-------|
| Search only finds MEMORY.md + daily logs | Search finds ALL your notes |
| Must manually know where to look | Semantic search across everything |
| "I don't have that information" | Finds connections you forgot existed |
Make your past conversations searchable too. Add this to your Clawdbot config:
"memorySearch": {
"sources": ["memory", "sessions"],
"query": {
"minScore": 0.3,
"maxResults": 20
}
}What this does: Indexes your conversation transcripts alongside your notes. Now when you ask "what did we discuss about X last week?" — it can actually find it.
Create MEMORY.md in workspace root - this is your curated long-term memory:
# MEMORY.md — Long-Term Memory
## About [Human's Name]
- Role/occupation
- Key goals and motivations
- Communication preferences
- Important relationships
## Active Context
- Current focus areas
- Ongoing projects (summaries, not details)
- Deadlines or time-sensitive items
## Preferences & Patterns
- Tools and workflows they prefer
- Decision-making style
- Pet peeves and likes
## Lessons Learned
- What worked
- What didn't
- Principles discovered
## Key Dates
- Birthdays, anniversaries
- Recurring events
- Important milestonesAdd these instructions to your AGENTS.md:
## Memory
You wake up fresh each session. These files are your continuity:
- **Daily notes:** `memory/YYYY-MM-DD.md` — raw logs of what happened
- **Long-term:** `MEMORY.md` — curated memories (like human long-term memory)
- **Topic notes:** `notes/` — organized by PARA structure (all searchable via memory_search)
### Writing Rules
- If it has future value, write it down NOW
- Don't rely on "mental notes" — they don't survive restarts
- Text > Brain 📝
### PARA Structure
- **Projects** (`notes/projects/`) — Active work with end dates
- **Areas** (`notes/areas/`) — Ongoing responsibilities (health, finances, relationships)
- **Resources** (`notes/resources/`) — Reference material, how-tos, research
- **Archive** (`notes/archive/`) — Completed or inactive items
### Memory Flush Protocol
Monitor your context usage with `session_status`. Before compaction wipes your memory, flush important context to files:
| Context % | Action |
|-----------|--------|
| < 50% | Normal operation |
| 50-70% | Write key points after substantial exchanges |
| 70-85% | Active flushing — write everything important NOW |
| > 85% | Emergency flush — full summary before next response |
| After compaction | Note what context may have been lost |
**The rule:** Act on thresholds, not vibes. If it's important, write it down NOW.Your agent's context window is finite. When it fills up, older context gets compacted or lost. Don't lose important information.
Run session_status periodically. Look for:
📚 Context: 36k/200k (18%) · 🧹 Compactions: 0| Context % | What to Do |
|-----------|------------|
| < 50% | Normal operation. Write decisions as they happen. |
| 50-70% | Increased vigilance. Write key points after each substantial exchange. |
| 70-85% | Active flushing. Write everything important to daily notes NOW. |
| > 85% | Emergency flush. Stop and write full context summary before responding. |
| After compaction | Immediately note what context may have been lost. Check continuity. |
notes/areas/open-loops.mdBefore a long session ends or context gets high:
The core question: "Will future-me thank me for this?"
Before saving any curated note:
Use these for structured, high-quality entries in notes/resources/:
# [CONCEPT NAME]
## What It Is
[One-line definition]
## Why It Matters
[What problem it solves, when you'd need it]
## How It Works
[Explanation with examples]
## Key Insight
[The "aha" moment — what makes this click]# [TOOL NAME]
**Category:** [devtools | productivity | etc.]
## What It Does
[Brief description]
## Why I Use It
[What problem it solved for YOU]
## When to Reach For It
[Scenarios where this is the right choice]
## Gotchas
- [Things that tripped you up]# [PATTERN NAME]
## Problem
[What situation triggers this pattern]
## Solution
[The approach]
## Trade-offs
**Pros:** [Why this works]
**Cons:** [When NOT to use it]PARA is a knowledge organization system created by Tiago Forte, author of Building a Second Brain. It organizes everything into four categories based on actionability:
What: Work with a deadline or end state
Examples: "Launch website", "Plan trip to Japan", "Finish client proposal"
File as: notes/projects/website-launch.md
What: Ongoing responsibilities with no end date
Examples: Health, finances, relationships, career development
File as: notes/areas/health.md, notes/areas/dating.md
What: Reference material for future use
Examples: Research, tutorials, templates, interesting articles
File as: notes/resources/tax-guide.md, notes/resources/api-docs.md
What: Inactive items from the other categories
Examples: Completed projects, outdated resources, paused areas
Move to: notes/archive/ when done
Create memory/YYYY-MM-DD.md for each day:
# YYYY-MM-DD
## Key Events
- [What happened, decisions made]
## Learnings
- [What worked, what didn't]
## Open Threads
- [Carry-forward items]memory/YYYY-MM-DD.mdnotes/ folderIs it about today specifically?
→ memory/YYYY-MM-DD.md
Is it a task with an end date?
→ notes/projects/
Is it an ongoing responsibility?
→ notes/areas/
Is it reference material for later?
→ notes/resources/
Is it done or no longer relevant?
→ notes/archive/
Is it a distilled lesson or preference?
→ MEMORY.md| Daily Logs | MEMORY.md |
|------------|-----------|
| Raw, timestamped | Curated, organized |
| Everything captured | Only what matters |
| Chronological | Topical |
| High volume | Condensed |
| "What happened" | "What I learned" |
Daily logs are your journal. MEMORY.md is your wisdom.
Pairs well with memory-setup for technical config and proactive-agent for behavioral patterns.
Generated Mar 1, 2026
A freelance designer uses PARA to track client projects, manage design resources, and archive completed work. The agent searches across notes to recall project decisions and client preferences, ensuring continuity between sessions.
A PhD student organizes research notes by projects (thesis chapters), areas (teaching responsibilities), resources (papers), and archive (completed studies). Semantic search helps retrieve relevant literature and past discussions with advisors.
A startup founder tracks active projects like product launches, areas like customer support, resources like templates, and archives old campaigns. The agent uses indexed session transcripts to review past strategy meetings and avoid context loss.
An individual organizes personal goals, health tracking, hobby resources, and archived events. The agent searches across all notes to provide insights on habits or recall important dates, leveraging the symlink for full knowledge base access.
A consultant manages multiple client engagements as projects, with areas for industry research and resources for methodologies. The agent retrieves client-specific notes and session histories to maintain context and improve service delivery.
Offer the basic PARA skill for free to attract users, then charge for premium features like advanced analytics, cloud sync, or integration with other tools. Revenue comes from subscriptions or one-time purchases for enhanced functionality.
Provide paid services to help businesses or individuals set up and optimize their PARA systems, including training, custom configurations, and integration with existing workflows. Revenue is generated through hourly rates or project-based fees.
Sell pre-made templates for different industries (e.g., academic, business) within the PARA structure, such as project outlines or resource guides. Revenue comes from template sales or bundling with the skill package.
💬 Integration Tip
Ensure the symlink is correctly set up to make all notes searchable, and regularly update MEMORY.md with curated insights to maximize the agent's effectiveness.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Create, search, and manage Bear notes via grizzly CLI.
Track water and sleep with JSON file storage
Notion API for creating and managing pages, databases, and blocks.
Smart ClawdBot documentation access with local search index, cached snippets, and on-demand fetch. Token-efficient and freshness-aware.
Work with Obsidian vaults as a knowledge base. Features: fuzzy/phonetic search across all notes, auto-folder detection for new notes, create/read/edit notes with frontmatter, manage tags and wikilinks. Use when: querying knowledge base, saving notes/documents, editing existing notes by user instructions.