From second-brain
Connect Claude Code and Obsidian to the second-brain tooling. Run once after cloning, or any time the setup may have drifted.
How this skill is triggered — by the user, by Claude, or both
Slash command
/second-brain:initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Connect Claude Code and Obsidian to the second-brain tooling. Run once after cloning, or any time the setup may have drifted.
Connect Claude Code and Obsidian to the second-brain tooling. Run once after cloning, or any time the setup may have drifted.
/second-brain:init [vault-path]
vault-path is optional. When provided it overrides the path in settings.json and CLAUDE.md.
Run scripts/init.sh [vault-path] from the repository root and report the output.
The script performs these checks in order:
jq and python3 are installedchmod +x any scripts missing executable bitshooks/hooks.json is well-formed JSONSECOND_BRAIN_VAULT_PATH env → settings.json → CLAUDE.mdDaily/, Ideas/, References/, etc.)Templates/ directory (idempotent — skips existing files)If all checks pass, complete the Obsidian side manually:
TemplatesYYYY-MM-DD, folder to Dailynpx claudepluginhub masuda-so/second-brainCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.