agentleFS
DanaResearchGroupDanaResearchGroup/agent-skills/obsidian-vault/SKILL.md

obsidian-vault

Skill1 starsChanged 3 months agoMITView on GitHub

Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.

62 other projects use a version of this, 44 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ubiquitous-language, batch-grill-me and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • kennethkeimSkill

    ubiquitous-language

    Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

    Also in 32 projects that use this

  • boyingliu01Skill

    batch-grill-me

    A relentless interview that asks every frontier question at once, round by round. Thin alias of `grilling` (#540) — upstream mattpocock/skills absorbed this protocol into grilling; XP-Gate keeps this name as the sprint-flow Phase 2 entry point so orchestration docs stay stable.

    Also in 6 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 26 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 25 projects that use this

  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 4 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 16 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

6 rules. 1 is common, 2 are distinctive, and 3 are very specific to this project.

  • 1

    Common

    Most of the 56 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When unsure where a note goes, search for sibling notes on the same topic and match their folder.

    line 27
  2. Very specific:

    Use Obsidian [[wikilinks]] syntax: [[Note Title]]

    line 85
  3. Distinctive:

    Update or add to the relevant index note when creating a new note

    line 87
  4. Very specific:

    Use Title Case for the filename — this is a Vault note.

    line 106
  5. Common:

    Write content as a self-contained unit of learning

    line 108
  6. Very specific:

    Add [[wikilinks]] to related notes at the bottom.

    line 109

“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Obsidian Vault

Vault location

~/Dropbox/Apps/remotely-save/Vault/

(Synced via Dropbox / remotely-save.)

Structure

Organized into topical folders at the root — place a note in the folder that fits its topic:

  • Code/ — dev/infra knowledge, per-project subfolders (Code/ARC, Code/T3, Code/Carmel)
  • knowledge/ — general knowledge (knowledge/wiki/ for wiki-style runbooks/guides)
  • tools/ — tool cheatsheets & indexes
  • HQ/ — the HQ workspace (read HQ/CLAUDE.md before operating on it)
  • Research/, Companies/, Group/, Teaching/, Meetings/, ViceDean/ — domain notes
  • CLAUDE.md at the vault root — the authority for naming, dates and language (§ A5). Read it before naming any file, in the vault or elsewhere in Dropbox. Also learnings.md and a few other loose notes.

When unsure where a note goes, search for sibling notes on the same topic and match their folder.

Naming conventions

Two different conventions live in the same Dropbox tree. Check which one applies before naming anything.

WhereConvention
Inside the Vault (~/Dropbox/Apps/remotely-save/Vault/)Title Case, no date — Tools Index.md. A few legacy index notes are lowercase (knowledge/wiki/index.md).
Elsewhere in Dropbox (~/Dropbox/remote-work/, and any other non-Vault Dropbox folder)YYYY.MM.DD <a|b|c> <Name>.<ext> — e.g. 2026.08.26 a ERC B1 Science Skeleton.md. See the letter rule below.

The letter

It is per document, per day. The letter distinguishes successive versions of one document saved on one date. It restarts at a on every new date, and a document not yet saved today starts at a no matter what else was saved today. It is not a running version number, and it is not a counter over the folder.

2026.08.12 a TS Metrics.pdf
2026.08.12 b TS Metrics.pdf     <- second version of THAT document, same day
2026.08.13 a TS Metrics.pdf     <- NEW DATE, back to "a" - not "c"
2026.08.13 a Other Report.md    <- different document, also "a" - letters do not run across docs

To pick it: list what exists for today's date with the same document name, and take the next unused letter.

DIR="$HOME/Dropbox/remote-work/SCM"; D=$(date +%Y.%m.%d); NAME="ERC B1 Science Skeleton"
ls "$DIR" | grep -c "^$D . $NAME\."      # 0 -> "a", 1 -> "b", 2 -> "c", ...

The live version of a document is its newest date, then the highest letter within that date.

The name

<Name> is Title Case, in both locations — 2026.08.26 a ERC B1 Science Skeleton.md, not 2026.08.26 a ERC B1 science skeleton.md. Acronyms keep their own casing. Both locations hold legacy files that disagree — the lowercase index notes in the Vault, sentence-case files in Dropbox — and they predate the rule rather than qualifying it; they are not worth renaming, so do not take a neighbour's casing as the convention.

Authority: Vault/CLAUDE.md § A5 "Naming, dates and language", which also fixes date formats (DD/MM/YYYY in HQ, ISO YYYY-MM-DD in knowledge/), English for all structure (filenames, frontmatter, headings — bodies follow the source language), and preserving upstream spelling in pointers including mistakes (the Dropbox folder really is 02.1_Catalouge).

⚠️ The failure mode is real. The Vault has zero files named with the dated pattern and remote-work/ has many, so matching whichever sibling file you happen to see first gets it wrong half the time. Match the location, not the nearest filename — and when a folder's existing files disagree with the rule, the rule wins.

  • Index notes aggregate related topics (e.g. Tools Index.md, knowledge/wiki/index.md) — just lists of [[wikilinks]]

Linking

  • Use Obsidian [[wikilinks]] syntax: [[Note Title]]
  • Link related/dependency notes at the bottom of each note
  • Update or add to the relevant index note when creating a new note

Workflows

Search for notes

VAULT="$HOME/Dropbox/Apps/remotely-save/Vault"
# By filename
find "$VAULT" -name "*.md" | grep -i "keyword"
# By content
grep -rl "keyword" "$VAULT" --include="*.md"

Or use Grep/Glob tools directly on the vault path.

Create a new note

  1. Pick the right folder (match sibling notes on the topic)
  2. Use Title Case for the filename — this is a Vault note. For a file landing outside the Vault in Dropbox, use YYYY.MM.DD <a|b|c> <Name>.<ext> instead (see Naming conventions)
  3. Write content as a self-contained unit of learning
  4. Add [[wikilinks]] to related notes at the bottom; add it to the relevant index note

Find related notes (backlinks)

grep -rl "\\[\\[Note Title\\]\\]" "$HOME/Dropbox/Apps/remotely-save/Vault"

Find index notes

find "$HOME/Dropbox/Apps/remotely-save/Vault" -iname "*Index*"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.