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. Tri
Real data. Real impact.
Emerging
Developers
Per week
Open source
Skills give you superpowers. Install in 30 seconds.
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.
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, APIsprivate/ --> Personal only notes/ --> Scratchpad, drafts journal/ --> Dated reflections
Example domains:
programmingdevopsdesignbusinessdatasecurityproductivityFor 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 NAMECategory: [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 NAMEProblem: [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/_indexTOOLBOX 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_KEYGet 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" } } }
No automatic installation available. Please visit the source repository for installation instructions.
View Installation Instructions
1,500+ AI skills, agents & workflows. Install in 30 seconds. Part of the Torly.ai family.
© 2026 Torly.ai. All rights reserved.