second-brainPersonal 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".
Install via ClawdBot CLI:
clawdbot install christinetyip/second-brainA 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.
Your second brain should:
Before saving: Will future-me thank me for this?
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/ --> Dated reflectionsExample domains: programming, devops, design, business, data, security, productivity
For understanding how something works:
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]
[ASCII diagrams for architecture/flows where helpful]
+----------+ +----------+
| Client | ---> | Server |
+----------+ +----------+
Key insight:
[The "aha" moment - what makes this click]
Related: [links to related concepts]For tools and technologies you've actually used:
TOOL NAME
Category: [category]
Website: [url]
Cost: [free/paid/freemium]
What it does:
[Brief description]
Why I use it:
[Personal experience - what problem it solved for you]
When to reach for it:
[Scenarios where this is the right choice]
Quick start:
[Minimal setup/usage to get going]
Gotchas:
[Things that tripped you up]For reusable solutions:
PATTERN NAME
Problem:
[What situation triggers this pattern]
Solution:
[The approach, with code/pseudocode if relevant]
Trade-offs:
[Pros and cons, when NOT to use it]
Example:
[Concrete implementation]For quick-lookup material:
REFERENCE: [TOPIC]
[Organized, scannable content]
[Tables, lists, code snippets]
[Minimal prose, maximum signal]Always confirm before saving:
When relevant topics come up:
Before saving, verify:
Use the wrapper script:
{baseDir}/scripts/ensue-api.sh <method> '<json_args>'Search knowledge:
{baseDir}/scripts/ensue-api.sh discover_memories '{"query": "how does X work", "limit": 5}'List by namespace:
{baseDir}/scripts/ensue-api.sh list_keys '{"prefix": "public/concepts/", "limit": 20}'Get specific entries:
{baseDir}/scripts/ensue-api.sh get_memory '{"key_names": ["public/concepts/programming/recursion"]}'Create entry:
{baseDir}/scripts/ensue-api.sh create_memory '{"items":[
{"key_name":"public/concepts/domain/name","description":"Short description","value":"Full content","embed":true}
]}'Update entry:
{baseDir}/scripts/ensue-api.sh update_memory '{"key_name": "public/toolbox/_index", "value": "Updated content"}'Delete entry:
{baseDir}/scripts/ensue-api.sh delete_memory '{"key_name": "public/notes/old-draft"}'Maintain public/toolbox/_index as master reference:
TOOLBOX INDEX
=============
Categories:
languages/ Programming languages
frameworks/ Libraries and frameworks
devtools/ Development utilities
infrastructure/ Deployment, hosting, CI/CD
productivity/ Workflow and productivity tools
data/ Databases, analytics, data tools
Recent additions:
[tool] - [one-line description]
Browse: "show my toolbox" or "what tools do I have for [category]"| User says | Action |
|-----------|--------|
| "save this", "remember this" | Draft entry, confirm, save |
| "what do I know about X" | Search and retrieve relevant entries |
| "add [tool] to toolbox" | Create toolbox entry |
| "list my [domain] concepts" | list_keys for that namespace |
| "show my toolbox" | Show toolbox index |
| "update [entry]" | Fetch, show diff, update |
| "delete [entry]" | Confirm, delete |
| "search for [topic]" | Semantic search across all knowledge |
Requires ENSUE_API_KEY environment variable.
Get your key at: https://www.ensue-network.ai?utm_source=clawdbot&utm_medium=workflow
Configure in clawdbot.json:
"skills": {
"entries": {
"second-brain": {
"apiKey": "your-ensue-api-key"
}
}
}Generated Mar 1, 2026
A new developer uses the skill to save key concepts and tools learned during onboarding, such as understanding microservices architecture or setting up CI/CD pipelines. This creates a personalized knowledge base that accelerates future reference and reduces reliance on team members for repetitive questions.
A consultant captures insights from client projects, including business patterns and tool recommendations, into structured entries. This enables efficient retrieval for similar future engagements, ensuring consistent advice and leveraging past learnings to deliver higher value.
A researcher saves complex concepts, methodologies, and data analysis tools in a structured format for easy recall. This helps in writing papers or preparing lectures by quickly accessing well-documented explanations and examples from past work.
An engineer documents tools like Kubernetes or Terraform with personal usage notes, gotchas, and quick-start guides. This serves as a living reference for troubleshooting and onboarding new team members, improving operational efficiency.
A product manager stores concepts related to agile methodologies, user research patterns, and productivity tools. This supports decision-making by providing retrievable insights from past projects and helps in building a reusable knowledge foundation.
Offer a free tier with limited storage or API calls to attract individual users, then charge for premium features like advanced search, team collaboration, or increased limits. Revenue comes from monthly subscriptions, targeting professionals and small teams seeking organized knowledge management.
Sell customized versions to large organizations with features like enhanced security, compliance tools, and integration with existing systems. Revenue is generated through annual licenses and support contracts, focusing on industries like tech or consulting where knowledge retention is critical.
Monetize the underlying API by allowing developers to integrate the knowledge base functionality into their own applications. Charge based on usage metrics such as API calls or data volume, appealing to businesses building custom tools or educational platforms.
💬 Integration Tip
Integrate this skill into workflows by setting up automated triggers for saving key insights after meetings or coding sessions, and use the search functionality to surface relevant knowledge during planning phases.
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Search and analyze your own session logs (older/parent conversations) using jq.
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", entity CRUD, or cross-skill data access.
Ultimate AI agent memory system for Cursor, Claude, ChatGPT & Copilot. WAL protocol + vector search + git-notes + cloud backup. Never lose context again. Vibe-coding ready.
Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection