- Productivity
- Obsidian
- Claude md
- Second brain
- Clients
- Weekly review
Obsidian Business Vault
Build an Obsidian vault that runs your business, not just your notes: eight folders (clients with a log per call, projects with their next milestone, operations, marketing, finances, team, knowledge, and a Generated folder for Claude's output) and SYSTEM/CLAUDE.md, which says who you serve, how you make money and how you write. Ships three workflows that use it: a 5-minute pre-call brief, call logging that makes every next brief sharper, and weekly/quarterly reviews. Use on "set up my vault", "build my vault like a business", "brief me for my call with…", "log this call", "weekly review".
SKILL.md
Obsidian Business Vault
Your notes do not do anything. A folder of markdown is a filing cabinet; a vault with conventions is a machine. This skill builds the machine and then runs it.
The structure (eight folders):
| Folder | What goes in it |
|---|---|
SYSTEM/ |
CLAUDE.md, voice examples, workflows, templates, dashboards |
01-Clients/ |
one folder per client, one log per call (calls/) |
02-Projects/ |
one folder per project, with its next milestone |
03-Operations/ |
how the business actually runs: SOPs, checklists, tools |
04-Marketing/ |
offers, content, campaigns |
05-Finances/ |
income, expenses, invoices, and numbers.md (the one number you watch) |
06-Team/ |
people you work with and what they own |
07-Knowledge/ |
references and research worth keeping |
08-Generated/ |
where the system drops its own output: briefs/, reviews/ |
The engine is one file. SYSTEM/CLAUDE.md describes the business (who you
serve, how you make money, the one number you watch) and your voice (tone,
rhythm, the words you never use). Read it before every task, so everything you
write for them sounds like them.
The workflows (in workflows/, copied into the vault's SYSTEM/workflows/):
| Workflow | Say | Claude Code | Output |
|---|---|---|---|
| Pre-call brief | "brief me for my call with Bean There Café" | /brief Bean There Café |
08-Generated/briefs/ |
| Log a call | "log this call with …" + notes/transcript | /log-call Bean There Café |
call note + client updated |
| Weekly review | "do my weekly review" | /weekly-review |
08-Generated/reviews/ |
| Quarterly review | "do my quarterly review" | /quarterly-review |
08-Generated/reviews/ |
Logging calls is what makes it compound: every logged call feeds the next brief, and every weekly review feeds the quarterly one. Day 180 is sharper than day one.
Which job is this?
- Setting up ("set up my vault", "build my vault like a business", a vault with
no
SYSTEM/CLAUDE.md): do Set up below. - Running a workflow in a vault that already has
SYSTEM/CLAUDE.md: read it, then follow the matching file in the vault'sSYSTEM/workflows/(or this skill'sworkflows/if the vault copy is missing). Do not rebuild anything.
Set up
1. Find the vault and look first
Ask for the vault folder if you were not given one, then look without changing anything:
ls "$VAULT"
find "$VAULT" -maxdepth 2 -type d -not -path "*/.obsidian*" | head -40
find "$VAULT" -iname "CLAUDE.md" -not -path "*/.obsidian*"
No vault yet is fine: the script creates the folder, and they open it in Obsidian with "Open folder as vault".
2. Ask, in one message
- The business: what do you sell, who do you serve, and how do you make money?
- The one number you watch (MRR, booked calls a week, average deal size…)?
- Your voice: tone, rhythm, words you use, words you never use, and 3-5 short pieces you actually wrote that sound most like you.
- What is running now: current clients, projects, and anyone you work with.
- Start small or full? One folder first (clients only) or all eight now. The default advice: start with one folder and let it run.
Unanswered items stay as TODO: in CLAUDE.md. Never make them up.
3. Build it
Run the bundled script from this skill's folder. It never overwrites or deletes:
anything that exists is reported as kept.
# start with one folder: SYSTEM + 01-Clients + 08-Generated
bash scripts/scaffold.sh "$VAULT" --start-small --client "Bean There Café"
# or the full eight (re-running later adds whatever is missing)
bash scripts/scaffold.sh "$VAULT" \
--client "Bean There Café" --client "Shear Bliss Salon" \
--project "Website redesign" --person "Priya"
It writes SYSTEM/CLAUDE.md, SYSTEM/voice-examples.md, SYSTEM/workflows/
(the four workflows), SYSTEM/templates/ (Client, Call, Project, SOP, Invoice,
Person, Brief, Review), SYSTEM/views/ (Clients, Projects, Unpaid invoices as
Obsidian Bases), .claude/commands/ (the four slash commands), a root CLAUDE.md
that points at SYSTEM/CLAUDE.md, 05-Finances/numbers.md, and one folder +
profile note per client, project and person.
No shell? Create the same folders and copy the files by hand: templates/CLAUDE.system.md
becomes SYSTEM/CLAUDE.md, templates/CLAUDE.root.md the root CLAUDE.md,
workflows/* go to SYSTEM/workflows/, templates/* to SYSTEM/templates/,
views/* to SYSTEM/views/, commands/* to .claude/commands/.
4. Fill in SYSTEM/CLAUDE.md
Replace each TODO: with their answers, in their words. Paste their writing samples
into SYSTEM/voice-examples.md exactly as written. Keep CLAUDE.md short; it is read
on every task. If they gave the one number, add this week's line to 05-Finances/numbers.md.
In Obsidian: Settings, Core plugins, Templates, folder SYSTEM/templates. The views
need Obsidian 1.9+ with the Bases core plugin on.
5. Hand over with a first win
Tell them what was created, what was kept, and which CLAUDE.md lines are still TODO. Then give them the loop:
- After their next call: "log this call with Bean There Café" and paste the notes.
- Before the call after that: "brief me for my call with Bean There Café".
- Friday: "do my weekly review".
Frontmatter the vault uses
| Property | Values |
|---|---|
type |
client, call, project, sop, invoice, person, brief, review, numbers |
status |
clients: lead, active, paused, past · projects: planned, active, blocked, done · invoices: draft, sent, paid |
client |
the client folder name, e.g. bean-there-cafe |
next_step, next_date |
on clients, kept current by the log-call workflow |
milestone, due |
on projects |
amount, currency, issued, due, paid |
on invoices |
| dates | YYYY-MM-DD |
Rules
- Their existing notes, folders and templates stay as they are.
- The business, the voice and the samples come from them, never from you.
- Generated work goes in
08-Generated/. Only the updates a workflow lists may touch their own notes; ask before anything else. - Never invent a client fact, a number or something said on a call. Missing is missing; say so.
- Nothing gets deleted. Finished clients and projects move to an
_archive/folder in their area.
On a MyClawBots agent
The vault lives on the person's computer, so this works where the agent can reach
their files: Claude Code, Claude desktop with folder access, or an agent with a synced
vault folder. If you cannot reach it, ask the step 2 questions, give them their filled-in
SYSTEM/CLAUDE.md and the one command to run:
bash scripts/scaffold.sh ~/Documents/MyVault --start-small --client "Client name"
Files
24 files ship with this skill. They are installed beside the SKILL.md.
---
description: Pre-call brief for a client
argument-hint: <client name>
---
Read SYSTEM/CLAUDE.md, then follow SYSTEM/workflows/pre-call-brief.md exactly.
Input: $ARGUMENTS