agentleFS
Sign inStart free
loulanyueloulanyue/skills/skills/personal/obsidian-vault/SKILL.md

obsidian-vault

Skill231 starsChanged 4 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.

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 4

    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:

    No folders for organization - use links and index notes instead

    line 18
  2. Very specific:

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

    line 22
  3. Distinctive:

    Use Title Case for filename

    line 42
  4. Distinctive:

    Write content as a unit of learning (per vault rules)

    line 43
  5. Very specific:

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

    line 44
  6. Distinctive:

    If part of a numbered sequence, use the hierarchical numbering scheme

    line 45
  7. Very specific:

    Search for [[Note Title]] across the vault to find backlinks:

    line 49

“Common” is measured: kept by at least 6 in 10 of the 24 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

/mnt/d/Obsidian Vault/AI Research/

Mostly flat at root level.

Naming conventions

  • Index notes: aggregate related topics (e.g., Ralph Wiggum Index.md, Skills Index.md, RAG Index.md)
  • Title case for all note names
  • No folders for organization - use links and index notes instead

Linking

  • Use Obsidian [[wikilinks]] syntax: [[Note Title]]
  • Notes link to dependencies/related notes at the bottom
  • Index notes are just lists of [[wikilinks]]

Workflows

Search for notes

# Search by filename
find "/mnt/d/Obsidian Vault/AI Research/" -name "*.md" | grep -i "keyword"

# Search by content
grep -rl "keyword" "/mnt/d/Obsidian Vault/AI Research/" --include="*.md"

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

Create a new note

  1. Use Title Case for filename
  2. Write content as a unit of learning (per vault rules)
  3. Add [[wikilinks]] to related notes at the bottom
  4. If part of a numbered sequence, use the hierarchical numbering scheme

Find related notes

Search for [[Note Title]] across the vault to find backlinks:

grep -rl "\\[\\[Note Title\\]\\]" "/mnt/d/Obsidian Vault/AI Research/"

Find index notes

find "/mnt/d/Obsidian Vault/AI Research/" -name "*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.

Check your setup, free