Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Vault: an Obsidian system your agent actually runs

    1

    Most Obsidian kits hand you folders and templates and leave the upkeep to you.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Vault: an Obsidian system your agent actually runs

    Vault: an Obsidian system your agent actually runs

    Example session with this skill installed

    set me up with a vault

    (later the same day)

    ingest these:

    • renew my passport by 15 Nov
    • publish tideline v0.2 to crates.io
    • write the tideline README quickstart, but only once v0.2 is out
    • decide whether tideline releases move to GitHub Actions or stay on my local script
    • the boiler needs servicing, every autumn
    • fill in my context files, I keep putting it off
    • Read your context and instructions
    • Compiled the vault

    vault: two scenes

    Two real sessions with the vault skill, run against a scratch directory (~/notes below). Every file, path and diff is the actual output of the run, copied from disk, not a mock-up. The date in the sessions is the real run date, Sunday 2026-10-25.

    The point to watch: the agent never asks "where should this go?". It decides. The only questions it asks are the ones nothing in the vault can answer:

    when and

    in what order. And a task you hand it is written down once, in the note that owns it, never in a daily note.


    Scene 1: "set me up with a vault"

    You have no vault. You say one sentence.

    set me up with a vault

    Step 1: one question round, three questions, a default on each

    The skill finds no root CLAUDE.md, so it runs job 0 (greenfield). It asks everything it needs in a single round and recommends an answer to each.

    AskUserQuestion (1 of 1 round)
    
    1. Where should the vault live?
       - ~/Documents/notes   (Recommended)
       - Somewhere else (Other)
    
    2. What is this vault for?
       - Both in one vault   (Recommended: the Projects/Areas split keeps work and
                              life apart without needing two vaults)
       - Professional
       - Personal
    
    3. Obsidian plugins?
       - Proceed without them   (Recommended: I resolve template expressions myself;
                                 the dashboards render as code blocks until the
                                 plugins land)
       - I already have Tasks and Dataview
       - I already have Tasks, Dataview and Templater
    

    Your answers

    1. Other: ~/notes
    2. Both in one vault
    3. I already have Tasks and Dataview

    "Both" names no subject, and the skill will not invent one. It asks for it, once, together with the one real thing you need to do there:

    AskUserQuestion
    
    I need one area to seed, named from your life rather than from my guess.
    What is it, and what is the first thing on it?
    
       - Career
       - Health
       - Household
       - Something else (Other)
    

    Other: Household. First thing: compare home contents insurance quotes.

    That is the whole interview.

    Step 2: the agent builds it

    It copies the structure from the skill's references/templates/, puts CLAUDE.md in the root verbatim (checked with cmp, byte-identical), drops the note-type templates into _Templates/, resolves the <% tp.date.now(...) %> expressions itself (you have no Templater) and seeds the vault.

    Resulting tree, exactly as on disk:

    notes/
    ├── 0 Inbox/
    ├── 1 Daily/
    │   └── 2026/
    │       └── 10-October/
    │           └── 2026-10-25-Sunday.md
    ├── 2 Literature/
    ├── 3 Atlas/
    │   └── MOCs/
    │       └── Household MOC.md
    ├── 4 Projects/
    ├── 5 Areas/
    │   ├── Admin/
    │   │   └── _area.md
    │   └── Household/
    │       └── _area.md
    ├── 9 Archive/
    ├── CLAUDE.md
    ├── Home.md
    ├── _Assets/
    ├── _Management.md
    ├── _Templates/
    │   ├── Area.md
    │   ├── Atomic.md
    │   ├── Fleeting.md
    │   ├── Literature.md
    │   ├── MOC.md
    │   ├── Meeting.md
    │   ├── Note.md
    │   ├── Person.md
    │   ├── Project.md
    │   └── _daily.md
    ├── _Weekly/
    ├── context/
    │   ├── README.md
    │   ├── business.md
    │   ├── goals.md
    │   └── working-style.md
    ├── index.md
    └── log.md
    

    4 Projects/ is deliberately empty. The skill does not invent projects; they arrive when you have work.

    Step 3: the seed

    An empty vault teaches nothing, so a handful of things are created: today's daily, a catch-all area that every one-off will land in, one area of yours, and a map for it.

    ~/notes/5 Areas/Admin/_area.md

    ---
    created: "2026-10-25 16:35"
    type: area
    status: active
    tags: [area, area/admin]
    ---
    
    # Admin
    
    What maintaining this means: the catch-all. One-off tasks that belong to no project or area land here until they earn a home of their own.
    
    ## Open
    
    - [ ] Fill in context/working-style.md and context/goals.md
    
    ## Notes
    
    ```dataview
    LIST FROM "5 Areas/Admin" WHERE contains(string(up), "_area") SORT file.name ASC
    ```
    

    Admin is always created, whatever you said. It is where a task that belongs to nothing goes, so a vault without it would have a default destination that does not exist. Its first item is real: the context/ files are empty prompts.

    ~/notes/5 Areas/Household/_area.md

    ---
    created: "2026-10-25 16:35"
    type: area
    status: active
    tags: [area, area/household]
    ---
    
    # Household
    
    What maintaining this means: keeping the household running. Bills, insurance, repairs, the flat itself. Map: [[Household MOC]].
    
    ## Open
    
    - [ ] Compare home contents insurance quotes
    
    ## Notes
    
    ```dataview
    LIST FROM "5 Areas/Household" WHERE contains(string(up), "_area") SORT file.name ASC
    ```
    

    The area and its item both come from your answer. No dates: an invented date is worse than none.

    ~/notes/3 Atlas/MOCs/Household MOC.md

    ---
    created: "2026-10-25 16:35"
    type: moc
    tags: [moc]
    ---
    
    # Household
    
    Ideas and reference for running the household. The operational side lives in [[5 Areas/Household/_area|the Household area]].
    
    ## Notes
    
    ```dataview
    LIST FROM "3 Atlas" WHERE contains(string(up), this.file.name) SORT file.name ASC
    ```
    

    ~/notes/1 Daily/2026/10-October/2026-10-25-Sunday.md

    ---
    created: "2026-10-25 16:35"
    type: daily
    tags: [daily]
    ---
    
    # Sunday, 25 October 2026
    
    ## Plan
    
    A view, not storage. Open tasks live in the project or area that owns them.
    
    ```tasks
    not done
    (due before tomorrow) OR (happens before tomorrow)
    sort by due
    ```
    
    ## Log
    
    ## Notes
    

    The daily's ## Plan is a query, not a list. It shows whatever is due or startable by today, overdue included, and nothing is ever copied into it by hand. A daily gets prose and links; it never owns a checkbox.

    The agent also adds a row per new durable page to index.md, and one line per destination to log.md:

    
    | Page | Type | What it is |
    |---|---|---|
    | [[5 Areas/Admin/_area\|Admin]] | area | Catch-all for one-off tasks that belong to no project or area |
    | [[5 Areas/Household/_area\|Household]] | area | Keeping the household running: bills, insurance, repairs |
    | [[Household MOC]] | moc | Map of notes about running the household |
    
    
    2026-10-25 16:35 | ingest | / | scaffolded vault from the vault skill templates
    2026-10-25 16:35 | ingest | 5 Areas/Admin/_area.md | created catch-all area with first open item
    2026-10-25 16:35 | ingest | 5 Areas/Household/_area.md | created area with first open item
    2026-10-25 16:35 | ingest | 3 Atlas/MOCs/Household MOC.md | created MOC for the Household area
    

    The files in context/ are starter prompts, not content. Filling them in is the highest-value ten minutes you can spend here.

    Step 4: the handover

    Vault ready at ~/notes: Admin catch-all, Household area with its map, today's daily, context/ prompts to fill in later. Dump your todos at me and I'll file them.

    No tour of the folder scheme. You will learn it by using it.


    Scene 2: you dump some todos

    Later the same day. You do not name files, folders or dates (apart from the one you happen to have in your head). You just talk.

    ingest these:

    • renew my passport by 15 Nov
    • publish tideline v0.2 to crates.io
    • write the tideline README quickstart, but only once v0.2 is out
    • decide whether tideline releases move to GitHub Actions or stay on my local script
    • the boiler needs servicing, every autumn
    • fill in my context files, I keep putting it off

    Step 1: routing, decided, not asked

    The agent reads the vault's CLAUDE.md, then searches before concluding anything has no home, and checks for existing copies before writing (One task, one home):

    $ rg -il "tideline|boiler|passport|crates" . --glob '!CLAUDE.md' --glob '!_Templates'
    (no matches)
    
    $ rg -n "^- \[ \]" . --glob '!_Templates' --glob '!CLAUDE.md'
    ./5 Areas/Household/_area.md:14:- [ ] Compare home contents insurance quotes
    ./5 Areas/Admin/_area.md:14:- [ ] Fill in context/working-style.md and context/goals.md
    

    Routing it arrives at, with the reason each time:

    #ItemGoes toWhy
    1Renew passport, 15 Nov5 Areas/Admin/_area.md, ## OpenOne-off belonging to nothing, so the catch-all. Never the daily, even though you are talking to it today
    2Publish tideline v0.2new 4 Projects/Tideline/_project.mdA recurring subject with no folder, and three items share it. It has a ship event, so a project, not an area
    3tideline README quickstartsame projectSame subject; reads as not startable yet ("once v0.2 is out")
    4Decide: Actions or local scriptsame projectA question whose answer is a decision, so - [ ] Decide: ... in the owning project
    5Service the boiler, every autumn5 Areas/Household/_area.md, ## OpenHousehold is the existing area, and a boiler is plainly part of it
    6Fill in my context filesnothing writtenAlready open in Admin, same task, same home, so no second checkbox

    The agent did not ask where any of this goes. It had the answers. The one decision it will not make alone is creating the project, so that goes into the round below.

    Step 2: the single question round

    Everything the vault cannot know, in one round. The first option of each question is the recommended one, so "yes" costs a click and corrections come back through Other.

    AskUserQuestion (1 of 1 round)
    
    Plan as I'd file it: passport in Admin; a new Tideline project holding publish,
    README and the decision; boiler in Household. No dates beyond the passport's.
    
    1. Create a project "Tideline" (4 Projects/Tideline) for the three tideline items?
       - Yes, ongoing, no project-level dates   (Recommended)
       - Yes, with a real due or start date (Other)
       - No, file them under Admin
    
    2. Due dates? (Passport already has 15 Nov.)
       - None for the rest   (Recommended: I won't invent one)
       - I'll list some (Other)
    
    3. "README quickstart, once v0.2 is out" can't start yet. Start date?
       - None, it follows the publish item in order   (Recommended)
       - I'll give a start date (Other)
    
    4. Order in the new Tideline Open list?
       - Decide, Publish, README   (Recommended)
       - Something else (Other)
       (Admin: passport above Fill in context, since it has a date.
        Household: boiler above insurance quotes, same reason.)
    

    Your answers

    1. Yes, ongoing, no project-level dates
    2. Other: publish v0.2 by 2026-11-08, boiler by 2026-11-30, nothing else
    3. Other: start 2026-11-09, the day after I plan to publish
    4. Other: publish, README, and decide after. I'm shipping v0.2 with the local script anyway

    Step 3: the result, as exact diffs

    Nothing was deleted or rewritten. One new file, and lines added to four existing ones.

    New file, ~/notes/4 Projects/Tideline/_project.md:

    ---
    created: "2026-10-25 16:36"
    type: project
    status: active
    tags: [project, project/tideline]
    ---
    
    # Tideline
    
    What shipping looks like: v0.2 published to crates.io, with a README quickstart.
    
    ## Open
    
    - [ ] Publish tideline v0.2 to crates.io 📅 2026-11-08
    - [ ] Write the tideline README quickstart 🛫 2026-11-09
    - [ ] Decide: GitHub Actions for releases, or keep the local release script
    
    ## Notes
    
    ```dataview
    LIST FROM "4 Projects/Tideline" WHERE contains(string(up), "_project") SORT file.name ASC
    ```
    

    The project has no start: or due: of its own, as you said. The dates live on the tasks.

    5 Areas/Admin/_area.md

    @@ -12,4 +12,5 @@ What maintaining this means: the catch-all. One-off tasks that belong to no proj
    
     ## Open
     
    +- [ ] Renew passport 📅 2026-11-15
     - [ ] Fill in context/working-style.md and context/goals.md
     
    

    5 Areas/Household/_area.md

    @@ -12,4 +12,5 @@ What maintaining this means: keeping the household running. Bills, insurance, re
    
     ## Open
     
    +- [ ] Service the boiler (every autumn) 📅 2026-11-30
     - [ ] Compare home contents insurance quotes
     
    

    index.md

    @@ -15,2 +15,3 @@ states status.
    
     | [[5 Areas/Household/_area\|Household]] | area | Keeping the household running: bills, insurance, repairs |
     | [[Household MOC]] | moc | Map of notes about running the household |
    
    +| [[4 Projects/Tideline/_project\|Tideline]] | project | Side project: tideline, v0.2 release and docs |
    

    log.md

    @@ -16,2 +16,5 @@ Ops: `ingest | edit | decide | lint | archive | distill | context-edit`
     2026-10-25 16:35 | ingest | 5 Areas/Household/_area.md | created area with first open item
     2026-10-25 16:35 | ingest | 3 Atlas/MOCs/Household MOC.md | created MOC for the Household area
    +2026-10-25 16:36 | edit | 5 Areas/Admin/_area.md | added 1 open item (passport, due 2026-11-15)
    +2026-10-25 16:36 | edit | 5 Areas/Household/_area.md | added 1 open item (boiler service, due 2026-11-30)
    +2026-10-25 16:36 | ingest | 4 Projects/Tideline/_project.md | created project with 3 open items (1 decision, 1 start-gated)
    

    Today's daily note is not in this list. It was not touched: it holds no tasks, and its ## Plan query will pick the passport, the release and the boiler up on their own when their dates come round.

    After the round, the whole vault holds each open task exactly once, and the daily holds none:

    $ rg -n "^- \[ \]" . --glob '!_Templates' --glob '!CLAUDE.md'
    ./4 Projects/Tideline/_project.md:14:- [ ] Publish tideline v0.2 to crates.io 📅 2026-11-08
    ./4 Projects/Tideline/_project.md:15:- [ ] Write the tideline README quickstart 🛫 2026-11-09
    ./4 Projects/Tideline/_project.md:16:- [ ] Decide: GitHub Actions for releases, or keep the local release script
    ./5 Areas/Admin/_area.md:14:- [ ] Renew passport 📅 2026-11-15
    ./5 Areas/Admin/_area.md:15:- [ ] Fill in context/working-style.md and context/goals.md
    ./5 Areas/Household/_area.md:14:- [ ] Service the boiler (every autumn) 📅 2026-11-30
    ./5 Areas/Household/_area.md:15:- [ ] Compare home contents insurance quotes
    
    $ rg -c "^- \[ \]" "1 Daily"
    (no matches)
    

    Step 4: the report

    The skill reports one line per thing done, no preamble:

    • Passport: Admin, due 2026-11-15.
    • Tideline: new project, +3 open (publish due 2026-11-08, README from 2026-11-09, decision last).
    • Boiler: Household, due 2026-11-30.
    • Context files: already open in Admin, not duplicated.

    What this shows

    • It decides. Six items, six routing decisions, zero "where should this go?" questions.

    One-offs have a home. The passport went to Admin, not into today's daily note. Nothing is ever dragged from one day to the next, because nothing is ever stored in a day.

    It asks only what the vault can't answer. Dates, start gates, order, and whether to create a project. One round, recommended option first.

    • It does not invent. No due dates you did not give, no project dates you did not need, no area you did not name.
    • It does not duplicate. The sixth item was recognised as already tracked and left alone.

    It leaves a trail. One line per destination in log.md, plain markdown, git-diffable, readable in Obsidian with the Tasks plugin the moment you open it.

    Planlog.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Most Obsidian kits hand you folders and templates and leave the upkeep to you. Six weeks later the Inbox is a shelf, half the notes have no parent, and your task list has three copies of the same thing.

    This ships the structure and the agent that maintains it. You talk, it files.

    "here's what I need to do this week" routes every item to the project or area that owns it, asking only about dates and order. "start my day" opens today, gives the next action per project and area, tells you what's due. "process my inbox" classifies every fleeting note and proposes a promotion table. "what did I do this week" fuses your dailies and your git history into themes, split done / in flight / blocked. "check the vault" finds duplicate tasks, orphans, broken links, stale claims and schema drift.

    No vault yet? It builds one, seeds it, and hands you a single next step. Vault already? It fits itself to yours and never moves one of your notes - brownfield adoption adds what's missing and describes what's there; restructuring is proposed, never applied.

    Personal and professional in one vault. The Projects/Areas split carries the separation.

    Two rules do the heavy lifting. Capture acts, deletion asks: additive changes just happen, destructive ones arrive as a table you approve. One task, one home: an open checkbox lives in exactly one note, which is what keeps a Tasks dashboard honest.

    Your vault ends up owning its own rules. The agent reads a CLAUDE.md at your vault root, so changing your schema changes its behaviour.

    What you need

    Obsidian, plus the Tasks and Dataview plugins for the dashboards (Templater optional). Without them it still works; the dashboards just render as code blocks until you install them.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Productivity.

    It writes into your notes, so the safety rules matter: additive changes happen directly, anything that moves, rewrites or deletes is proposed first. Brownfield adoption never moves an existing note; restructuring is proposed, not applied. Tasks syntax follows the Obsidian Tasks plugin (📅 due, 🛫 start); recurring tasks (🔁) are not handled yet. The weekly report reads git history only for repos you point it at.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 22 days ago

    Software
    ObsidianObsidian Tasks pluginObsidian Dataview pluginripgrep
    Optional
    Git

    Permissions

    Read Files
    Write Files
    Terminal / Shell

    Reads and writes Markdown inside your vault only. Additive changes (new notes, new tasks) happen directly; anything that moves, rewrites or deletes existing content is proposed as a table and applied only on your yes. Shell is used for the date, ripgrep searches, and read-only git log for the weekly report. No network access.

    Listed22 days ago

    What's inside

    Frequently Asked Questions

    A kit gives you folders and leaves the upkeep to you. This ships the structure plus the agent that keeps it in shape: it decides where each todo belongs, asks only about dates and order, drains your Inbox, reports your week and finds duplicates, orphans and broken links.

    Obsidian and an agent that reads SKILL.md (Claude Code, Cursor, Codex CLI). The Tasks and Dataview plugins power the dashboards; Templater is optional. ripgrep is used for search. You don't need to write any config: setup installs a CLAUDE.md at your vault root that describes the schema, and you can edit it.

    No. Capture acts, deletion asks: new notes and new tasks are written directly, and anything that moves, rewrites or deletes existing content arrives as a table you approve first.

    Either. With no vault, it builds one, seeds it and gives you one next step. With an existing vault, it writes a CLAUDE.md describing your structure, adds only what's missing, and never moves a note. Restructuring is proposed, never applied.

    The skill with all seven jobs (set up, capture, day, inbox, report, session rescue, sweep), 10 note templates, the Home and Management dashboards, and the CLAUDE.md that makes your vault own its rules. One-time purchase, use it on your own vaults forever.

    Ask "what did I do this week" or "prep for my 1on1". It reads your daily notes and, if you point it at repos, their git history, and groups the result into themes split done / in flight / blocked. For a 1on1 it frames the summary against your goals in context/goals.md. It offers to save the report as a note.

    New in Productivity