Browse / Second brain / agentic-workspace-template
agentic-workspace-template
spencermarx
Obsidian + Claude Code workspace template.
Open spencermarx/agentic-workspace-template → Checked against the four rules.
agentsclaude-codeknowledge-managementobsidiantemplate
Built for Claude Code
ships .claude CLAUDE.md and nothing for other agents.
In its own words
Nested CLAUDE.md progressive disclosure, standards routed to files by path glob, and a conversational bootstrap that generates the tree.
A GitHub template for knowledge workspaces that two interfaces share: Obsidian is the human GUI, Claude Code is the agentic GUI, both operating over the same Markdown files in one git repo.
Clone it, answer some questions, and you get a vault with a nested CLAUDE.md hierarchy, a standards layer that routes rules to the files they govern, a working Obsidian plugin set, and a skill library.
Use it
- Use this template on GitHub to create your repo, then clone it.
./hq bootstrap-- a conversation, not a form. It interviews you, generates the folder tree and theCLAUDE.mdhierarchy, and wires Obsidian../hq obsidian-setup-- writes per-machine plugin config. Quit Obsidian first.- Open the repo root in Obsidian as a vault, trust the plugins when prompted, and start at
Home.md.
Nothing to install. The engine is Python 3 standard library, and /usr/bin/python3 ships with the same Xcode Command Line Tools that provide git.
The one rule that holds it together
.workspace/, .claude/, .obsidian/, Workspace/Templates/, and .credentials/ are template-owned and contain no workspace content. Everything else is workspace-owned and contains no template logic. No file is both.
That boundary is what lets ./hq upgrade replace harness files without touching your notes.
License
MIT. Vendored third-party skills keep their own provenance and copyright; see THIRD-PARTY-NOTICES.md.
The repository's own description, then its whole README. Open the repo ↗
Read from the repository's git tree on 2026-08-17.