Skill Detail

Maintain a Claude Code and Obsidian second brain with second-brain-os

Use second-brain-os to give Claude Code a repeatable Obsidian knowledge-base workflow with skills, commands, agents, scripts, and a starter vault.

Developer ToolsClaude Code
Developer Tools Claude Code Security Reviewed
⭐ 888 GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill maintain-claude-code-and-obsidian-second-brain-with-second-brain-os Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Claude Code, Obsidian, Git, a local markdown vault, and the second-brain-os repo assets for skills, commands, agents, scripts, and starter vault content.
Install & setup
Clone https://github.com/undefined-ui/second-brain-os, create a local brain workspace, copy the repo's skills, commands, agents, scripts, and starter vault into the workspace's Claude Code and vault folders, then run Claude Code from that workspace and follow the documented quickstart.
Author
undefined-ui
Publisher
Organization
Last updated
Oct 4, 2026
Quick brief

Use this skill when a user wants a local knowledge base that an agent can maintain as an operating workflow, not just a folder of notes. The operator clones second-brain-os, copies its skills, commands, agents, scripts, and starter vault into an Obsidian-backed workspace, then runs Claude Code in that workspace to interview the user, process clipped inputs, create linked markdown pages, and keep the knowledge graph organized.

How it works

What this skill actually does

Invoke it when the task is to ingest articles, videos, saved references, project notes, and personal context into a structured second brain with reviewable markdown outputs. Do not use it as a generic Obsidian product listing or a vague memory-system recommendation; the boundary is the documented Claude Code workflow and repo-provided assets. Inputs are local files, clipped content, prompts, and the user’s vault conventions. Outputs should be linked notes, updated indexes, and explicit handoffs that can be reviewed in Git or Obsidian. Keep MCP access to Obsidian optional and supervised.