agentleFS
AlexisBalayreAlexisBalayre/claude-code-power-config/.claude/skills/obsidian-vault/SKILL.md

obsidian-vault

Skill2 starsChanged 30 days agoMITView on GitHub

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

  • Reads credentials

63 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 9 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 33 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 27 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

  • 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 26 projects that use this

  • RoentekSkill

    loop-me

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

    Also in 17 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

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

  • 2

    Common

    Most of the 56 edited versions we read keep these.

  • 1

    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. Very specific:

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

    line 34
  2. Common:

    Use Title Case for the filename

    line 54
  3. Common:

    Write content as a unit of learning

    line 55
  4. Very specific:

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

    line 56
  5. Distinctive:

    Place it in the appropriate subfolder (or the vault root for general index/topic notes)

    line 57
  6. Very specific:

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

    line 61

“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

A personal-workflow integration. It assumes your notes live in an Obsidian vault on disk and operates on them with the standard Read/Glob/Grep tools plus shell.

Vault location

Set OBSIDIAN_VAULT in .env (see .env.example), then source it in your shell (set -a; . ./.env; set +a) so the commands below resolve $OBSIDIAN_VAULT:

# .env
OBSIDIAN_VAULT="$HOME/Documents/notes"   # adjust to your vault

Typical subfolders (rename to match yours):

  • Daily Logbook/: daily notes (managed by /daily-note)
  • Templates/: note templates (e.g., Daily Log.md)

Naming conventions

  • Index notes: aggregate related topics (e.g., Skills Index.md, RAG Index.md)
  • Title Case for all note names
  • Daily notes use YYYY-MM-DD.md and live under Daily Logbook/

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

# Search by content
grep -rl "keyword" "$OBSIDIAN_VAULT" --include="*.md"

Or use the Grep/Glob tools directly on $OBSIDIAN_VAULT.

Create a new note

  1. Use Title Case for the filename
  2. Write content as a unit of learning
  3. Add [[wikilinks]] to related notes at the bottom
  4. Place it in the appropriate subfolder (or the vault root for general index/topic notes)

Find related notes

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

grep -rl "\\[\\[Note Title\\]\\]" "$OBSIDIAN_VAULT"

Find index notes

find "$OBSIDIAN_VAULT" -name "*Index*"

Related

  • The /daily-note skill manages the Daily Logbook/ subfolder; defer to it for daily notes.

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.