Who it is forA researcher or engineer who saves articles and videos all week and never rereads them, and wants them filed and linked without manual work.
The problemBookmarks and read-later queues pile up unconnected. Filing and linking them by hand stops after a few weeks.
The outcomeA local vault of markdown files where each clipped source becomes linked wiki pages that update existing pages instead of piling up beside them.
What you need first
- Git, to clone the repo
- Obsidian, to open the vault as a folder
- Claude Code, the agent the README sets up the vault around
- A terminal, for the copy commands and for running claude
Steps
git clone https://github.com/undefined-ui/second-brain-os.gitcp -r second-brain-os/vault-template ~/brainmkdir -p ~/brain/.claudethencp -r second-brain-os/skills ~/brain/.claude/skills,cp -r second-brain-os/commands ~/brain/.claude/commands,cp -r second-brain-os/agents ~/brain/.claude/agentsandcp -r second-brain-os/scripts ~/brain/scripts(inferred, check the README)rm ~/brain/.claude/*/README.md ~/brain/scripts/README.mdcd ~/brain && claude, then clip one article intoraw/with the Web Clipper and run/ingest- Open
~/brainin Obsidian with "Open folder as vault" and check the new pages and their links
Prompt for your agent
Using the second-brain-os repo, copy vault-template to ~/brain and copy skills, commands, agents and scripts into ~/brain/.claude and ~/brain/scripts. Place one article in ~/brain/raw/, run /ingest, and report the wiki pages created. Verify that every new page has at least one wikilink to another page.
Caveat. The README says the vault is built around Claude Code and Obsidian, so other agents will need the same markdown layout, and the folder READMEs must be removed so the agent does not read them as vault content.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page