Skill Overview
---
name: second-brain
description: Personal knowledge base powered by Ensue for capturing and retrieving understanding. Use when user wants to save knowledge, recall what they know, manage their toolbox, or build on past learnings. Triggers on "save this", "remember", "what do I know about", "add to toolbox", "my notes on", "store this concept".
metadata: {"clawdbot":{"emoji":"🧠","requires":{"env":["ENSUE_API_KEY"]},"primaryEnv":"ENSUE_API_KEY","homepage":"https://ensue-network.ai"}}
---
# Second Brain
A personal knowledge base for **building understanding that compounds over time**. Not a note dump - a structured system for capturing knowledge you can actually retrieve and use.
## Philosophy
Your second brain should:
- **Capture understanding, not just facts** - Write for your future self who forgot the context
- **Be retrievable** - Structured so you can find things when you need them
- **Stay evergreen** - No private details, credentials, or time-sensitive data
- **Reflect real experience** - Only save what you've actually learned or used
Before saving: *Will future-me thank me for this?*
## Namespace Structure
```
public/ --> Shareable knowledge
concepts/ --> How things work
[domain]/ --> Organize by topic
[concept-name] --> Individual concepts
toolbox/ --> Tools and technologies
_index --> Master index of tools
[category]/ --> Group by type
[tool-name] --> Individual tools
patterns/ --> Reusable solutions
[domain]/ --> Design patterns, workflows
references/ --> Quick-reference material
[topic]/ --> Cheatsheets, syntax, APIs
private/ --> Personal only
notes/ --> Scratchpad, drafts
journal/ --> DateBot Reviews(1)
Structured knowledge capture with a remote backing store
Builds a personal knowledge base organised into concepts, tools, patterns and references, split between a shareable area and a private one. The design pushes toward capturing understanding rather than raw facts, writing for a future reader who has lost the original context. Everything lives behind a hosted service and needs that provider's key before anything can be saved or retrieved, so an offline or keyless setup gets nothing. The guidance is explicit that credentials, personal details and time-sensitive material do not belong in it, which makes it the wrong shelf for secrets. The namespace layout pays off only once entries accumulate.
Use case: Keeping durable notes on concepts and tools
Study Guides(1)
Structured memory that compounds across sessions
Second Brain is a personal knowledge base for an agent, backed by the Ensue service. It is not a note dump. The point is to capture understanding in a shape a future session can actually retrieve, so learnings stack up instead of evaporating when the context window resets. ## What it does - Organizes knowledge into a fixed namespace tree: shareable concepts, a toolbox of tools and technologies, reusable patterns, and quick references, alongside private notes and journal entries. - Keeps a master toolbox index so the agent knows which tools it already has before starting new work. - Pushes the writer to explain for a future reader who has lost the surrounding context, and to save only what was genuinely used or learned. ## When it is the wrong choice Do not treat this as a scratchpad. The design keeps credentials, private details, and time-sensitive data out of the retrievable namespaces, so it is the wrong place to stash secrets or a customer list. It also depends on the Ensue service and a configured api key, so an offline session or a key-less one has no backing store at all. ```bash # namespace layout the agent writes into public/concepts/[domain]/[concept-name] public/toolbox/_index public/patterns/[domain] public/references/[topic] private/notes private/journal ``` ## Notes A useful habit is to revisit the toolbox index after any session that added a tool, because the index is what makes recall fast. Treat each entry as a small explainer for a stranger, not a bookmark.
Quick Facts
Install
npx clawhub@latest install 1