By srbdp
BrainLift maintenance toolkit — workspace setup, add sources, query knowledge, audit health, evidence graph, Obsidian linking
Parses a BrainLift markdown file into structured sections for use by other skills and agents
Detects URL type and fetches structured content from Twitter/X, articles, YouTube, and general web pages
Extracts DOK1 facts, generates DOK2 summaries, and brainstorms cross-source DOK3 insights from a single source URL for BrainLift Knowledge Trees
Analyzes BrainLift health across 6 categories — evidence chains, token health, semantic quality, freshness, structure, and completeness
Set up a BrainLift workspace in the current directory — creates folder structure, config, and pointer file
Health-check your BrainLift — audit evidence chains, token counts, semantic quality, freshness, and completeness
Ask questions against your BrainLift — get cited answers, discover gaps, and compound your explorations back into knowledge
Add new content to an existing BrainLift - paste a URL and your thoughts, get guided through the update
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin that helps you build and maintain BrainLifts — structured knowledge artifacts for developing real expertise in any domain.
The plugin handles the bookkeeping that kills knowledge bases: extracting facts, generating summaries, tracking evidence chains, flagging stale content, and keeping everything organized. You focus on the curation decisions that actually build expertise — what to include, what challenges your thinking, what patterns you see across sources.
Inspired by Karpathy's LLM Wiki pattern: the LLM maintains the knowledge base, you direct the analysis.
A BrainLift is a structured markdown file where you develop expertise on a focused topic. It organizes knowledge in layers:
Purpose (what's in/out of scope)
DOK4 - SPOVs (your expert positions — "spiky points of view")
DOK3 - Insights (surprising patterns you've found across sources)
────── your expertise is above / external information is below ──────
Experts (people worth following)
Knowledge Tree
└─ Sources
├─ DOK2 - Summaries (patterns synthesized from a source's facts)
├─ DOK1 - Facts (specific, verifiable details extracted from the source)
└─ Link to original content
Each layer is supported by the one below it. Your SPOVs are backed by insights, which are backed by facts extracted from real sources. No unsupported claims.
.md files in a directory (use the BrainLift template to get started, or run /new-brainlift if you have the full BrainLifting project)In any Claude Code session, run these two commands:
/plugin marketplace add srbdp/brainlift-plugin
/plugin install bl@srbdp-brainlift
The first command adds the plugin marketplace from GitHub. The second installs the bl plugin from it. After that, the slash commands (/bl:init, /bl:update, /bl:query, /bl:lint) are available in every Claude Code session.
To update the plugin later, Claude Code will check for updates automatically. You can also force an update by re-running the install command.
Navigate to the folder where you want to keep your BrainLifts and run /bl:init:
cd ~/brainlifts # or wherever you want
/bl:init
This creates:
~/brainlifts/
├── CLAUDE.md # Workspace config (Claude Code loads this automatically)
├── index.md # Auto-generated catalog, evidence graph, source registry
├── lifts/ # Your BrainLift .md files go here
├── logs/ # Change logs (auto-managed by the plugin)
└── sources/ # Raw source content (optional, for URL rot insurance)
It also saves a pointer at ~/.brainlift so the plugin can find your workspace from any Claude Code session — you don't have to be in the BrainLift folder to use the commands.
If you have existing BrainLift files, /bl:init will detect them and offer to move them into lifts/ (and any companion .log.md files into logs/).
lifts/ keeps BrainLift files separate from logs, READMEs, and other markdown. ls lifts/ shows exactly your BrainLifts — nothing else.logs/ tracks how each BrainLift evolves over time without doubling the file count in your working directory.sources/ is for future use — the plugin will optionally save fetched source content here so you have a local copy if URLs break.CLAUDE.md serves double duty: it tells Claude Code about your workspace (loaded as project instructions when you cd in), and it contains a marker (<!-- brainlift-root -->) that the plugin uses to find your BrainLifts automatically.index.md is auto-generated — the plugin writes it, you read it. It catalogs all your BrainLifts, maps the evidence graph (which SPOVs are supported by which Insights, which draw from which Sources), and lists every source across all BrainLifts. The plugin reads this first for fast navigation. If you use Obsidian, the wikilinks in index.md light up the graph view.The plugin finds your BrainLifts automatically through a three-step cascade:
CLAUDE.md and finds lifts/ directly.~/.brainlift to find your workspace.You never have to re-specify the path after initial setup.
/bl:update — Add a source to your BrainLiftThe core workflow. Paste a URL and get guided through adding it to your BrainLift.
npx claudepluginhub srbdp/brainlift-plugin --plugin blSecond Brain OS — 16 skills for knowledge management, deep thinking, and vault operations powered by Obsidian.
LLM-maintained knowledge base skill — structured wiki with Obsidian, milestone-based source clustering, proactive write-back, and autonomous lint
Personal knowledge management with brain CLI - capture notes, manage todos, auto-sync, and search your second brain
A collection of Claude Code skills for knowledge management, wiki building, and more.
LLM-maintained personal wiki skills for Claude Code. Implements Karpathy's LLM Wiki pattern — persistent, compounding knowledge base for research, codebase documentation, or any long-term knowledge accumulation.
Kit completo de skills pra transformar uma pasta em vault Obsidian profissional + dashboard local com ML. 6 skills: init (scaffold), librarian (cura contínua), migrate (adoção não-destrutiva), organizer (clusters/duplicatas), expand (notas-ponte via LLM restrito), pulse (dashboard localhost com FSRS, recommendations, anomalies). 100% local, privacy-first, pt-br.