agentleFS
Sign inStart free
ntaffziintaffzii/Skill-Agents/skills/obsidian/obsidian-vault-workflow/SKILL.md

obsidian-vault-workflow

Skill4 starsChanged 2 months agoMITView on GitHub

Operate across an Obsidian vault: organize notes, maintain links, normalize tags and properties, create indexes, update maps of content, and preserve vault conventions. Use when the user asks to clean, organize, connect, refactor, or maintain an Obsidian vault.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when working across multiple notes.

    line 8
  2. Distinctive:

    Follow local style before introducing a new one.

    line 14
  3. Distinctive:

    Use wikilinks for internal relationships.

    line 23
  4. Distinctive:

    Keep aliases when renaming concepts.

    line 24
  5. Distinctive:

    Avoid breaking embedded files or block references.

    line 25
  6. Distinctive:

    Add index notes when a topic has multiple related notes.

    line 28
  7. Distinctive:

    Use sections like Overview, Notes, Projects, Questions, and Related.

    line 29
  8. Distinctive:

    Check renamed or moved files have aliases or updated references.

    line 35
  9. Distinctive:

    Do not mass-rename notes without explicit user approval.

    line 39
  10. Distinctive:

    Do not flatten a vault's existing structure just to make it neat.

    line 40
  11. Distinctive:

    Prefer incremental cleanup with clear before/after behavior.

    line 41
  12. Distinctive:

    Keep private or personal note content intact unless asked to rewrite it.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Workflow

Use this skill when working across multiple notes.

Workflow

  1. Discover conventions
    • Inspect existing folder names, note titles, tags, properties, templates, and index notes.
    • Follow local style before introducing a new one.
  2. Plan the change
    • Identify affected notes.
    • Preserve existing links.
    • Decide whether to create backlinks, index notes, or maps of content.
  3. Edit carefully
    • Update frontmatter consistently.
    • Use wikilinks for internal relationships.
    • Keep aliases when renaming concepts.
    • Avoid breaking embedded files or block references.
  4. Create navigation
    • Add index notes when a topic has multiple related notes.
    • Use sections like Overview, Notes, Projects, Questions, and Related.
    • Link both directions when a relationship is important.
  5. Verify
    • Check YAML frontmatter.
    • Check changed wikilinks.
    • Check renamed or moved files have aliases or updated references.

Rules

  • Do not mass-rename notes without explicit user approval.
  • Do not flatten a vault's existing structure just to make it neat.
  • Prefer incremental cleanup with clear before/after behavior.
  • Keep private or personal note content intact unless asked to rewrite it.

Output Format

End with:

  • Notes changed
  • Links, tags, or properties updated
  • Indexes or canvases created
  • Validation performed
  • Anything intentionally left untouched

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