Lean Obsidian
SimonTheSalesBooster/lean-obsidian
Sistema de 4 pastas que elimina decisões de arquivamento no Obsidian
Ver no GitHubSistema de 4 pastas para manter seu vault Obsidian limpo e organizado quando agentes IA escrevem diariamente nele. Implementa um pipeline de publicação simples que elimina decisões de arquivamento e reduz a sobrecarga cognitiva de gerenciar estruturas complexas.
Instalação
npx convez-ai SimonTheSalesBooster/lean-obsidian1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Criar pipelines de publicação para múltiplos canais de conteúdo
- Manter vaults limpos com escrita contínua de agentes IA
- Reduzir tempo gasto em organização de arquivos e decisões de filing
Veredito

Skill prático e opinioso que resolve um problema real: vaults Obsidian crescem desordenados. O modelo de 4 pastas com regras claras (Now, Channel Output x2, Timeless) é simples e funciona bem para trabalho em conhecimento com publicação. Excelente para quem usa Claude Code para automação.
README
A tradução para o português deste README ainda está na fila.
Lean Obsidian
4 folders. No filing system. A publishing pipeline.
Most Obsidian vaults look like this after 6 months: 00 Inbox, 01 Projects, 02 Areas, 03 Resources, 04 Archive, 05 Templates, 06 Meetings, 07 People, 08 Agents, 09 Board…
You spend more time deciding where to file things than using them.
Lean Obsidian is the opposite. Every folder has one job. The structure maps to what you're actually doing, not what you imagine you'll do later.
The 4-Folder System
| # | Folder | Job | Rule |
|---|---|---|---|
| 01 | Now | Active work today — agendas, drafts, immediate deliverables | Clear it daily |
| 02 | Sales Show (or your channel) | Content to publish — articles, scripts, posts | After publishing → move to 04 |
| 03 | Investing Show (or your channel) | Content to publish — second channel | After publishing → move to 04 |
| 04 | Timeless | Everything published, done, or reference | Permanent home |
Daily Notes and Excalidraw are auto-managed by plugins — don't touch them.
Why This Works
Folders 02 and 03 are your publish queue.
If a file is in 02 Sales Show, it still needs publishing. That's the only signal. You open the folder, you see work to do. After you publish — move it to 04 Timeless. Presence in the folder = open action. Absence = done.
No sub-folders. No dates. No tags. No decision needed.
Folder 04 is where everything lands when it's done.
Reference docs, published articles, agent logs, quarterly reviews, templates — all flat (or in existing sub-folders like Quarterly Reviews/). You search for things in 04. You don't file into it.
Folder 01 is cleared daily.
Anything that lives in 01 Now for more than 48 hours isn't "now" anymore. Move it to 04 or delete it.
The Problem This Solves
Knowledge workers create new folders when they're anxious. A new topic appears → create a folder. A new project starts → create a folder. Six months later, the vault has 40 folders and nobody can find anything.
The real cost isn't the extra folders. It's the cognitive load of re-deciding the structure every time you open Obsidian.
Lean Obsidian makes the decision once. Every file has exactly one place it can go.
Adapting the Channel Folders
Folders 02 and 03 are named for Simon's two content channels (The Sales Show and The Investing Show). Rename them for yours:
02 Newsletter+03 YouTube02 Blog+03 Podcast02 Client Work+03 Personal Projects
The logic stays the same: these folders are your active output queue. Files move through them on their way to 04 Timeless.
If you only have one output channel, use a single folder. If you have four, use four — but not more. The more folders, the more decisions.
Restoring the Structure (the /lean-obsidian skill)
Agents and habits add folders over time. This repo includes a Claude Code skill (lean-obsidian.md) that:
- Audits your vault for rogue folders
- Reports what doesn't belong
- Moves files to their correct home and removes the empty folders
Run /lean-obsidian in Claude Code whenever the vault drifts.
For Claude Code Users: Wiring the Hard Rule
Add this to your global workflow.md (or CLAUDE.md):
### Obsidian Vault — NO NEW FOLDERS
4 folders only: 01 Now, 02 [Channel], 03 [Channel], 04 Timeless.
Before writing any file: confirm folder exists. If unsure → 04 Timeless. Never create a new folder.
With this in your global rules, every Claude session knows the structure without being told.
Built by Strategy Sprints
Strategy Sprints runs 15 AI advisors that write to Obsidian daily — agent logs, board meetings, task queues, research briefs. We learned the hard way: give agents freedom to create folders and they will. Within weeks, a clean vault becomes a maze.
Lean Obsidian is the constraint that keeps it clean.
Strategy Sprints · Built with Claude Code