agentleFS
surasakchosurasakcho/claude-skills/obsidian-vault/SKILL.md

obsidian-vault

Skill0 starsChanged 5 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.

  • Reads credentials

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 2 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

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 9 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 4

    Common

    Most of the 56 edited versions we read keep these.

  • 0

    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. Common:

    No folders for organization - use links and index notes instead

    line 25
  2. Very specific:

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

    line 29
  3. Common:

    Use Title Case for filename

    line 49
  4. Common:

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

    line 50
  5. Very specific:

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

    line 51
  6. Common:

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

    line 52
  7. Very specific:

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

    line 56

“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

Machine-specific, so it is never hardcoded here. Read it once and reuse it for the session:

VAULT="$(python lib/skillconfig.py get OBSIDIAN_VAULT --repo <skills-repo> --prompt 'Obsidian vault path')"

First use prompts and stores it in the repo's gitignored .env; later uses read it back. If it is not set and nothing can prompt, stop and ask — do not guess a vault path.

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 "$VAULT" -name "*.md" | grep -i "keyword"

# Search by content
grep -rl "keyword" "$VAULT" --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\\]\\]" "$VAULT"

Find index notes

find "$VAULT" -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.