Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
julianobarbosa avatar

Obsidian Vault Management

  • 276 installs
  • 6 repo stars
  • Updated July 22, 2026
  • julianobarbosa/claude-code-skills

obsidian-vault-management is a Claude Code skill that organizes, refactors, links, and maintains an Obsidian vault so engineering notes, ADRs, runbooks, and project docs stay searchable and consistent for developers mana

About

obsidian-vault-management is a documentation skill from julianobarbosa/claude-code-skills that helps developers organize, refactor, link, and maintain Obsidian vaults used for engineering knowledge. The skill supports consistent structure for ADRs, runbooks, project notes, and cross-linked reference material so agents and humans can search and navigate technical docs reliably. Developers reach for obsidian-vault-management when vaults grow messy—duplicate pages, broken wikilinks, inconsistent tags, or scattered runbooks—and they need systematic cleanup without manual reorganization. It fits teams that treat Obsidian as the source of truth for internal engineering documentation alongside code repositories.

  • Vault organization patterns
  • Link and tag hygiene
  • Note refactoring
  • Knowledge base upkeep
  • Agent-friendly note workflows

Obsidian Vault Management by the numbers

  • 276 all-time installs (skills.sh)
  • +3 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #931 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/julianobarbosa/claude-code-skills --skill obsidian-vault-management

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs276
repo stars6
Last updatedJuly 22, 2026
Repositoryjulianobarbosa/claude-code-skills

How do you refactor a messy Obsidian engineering vault?

Organize, refactor, link, and maintain an Obsidian vault so engineering notes, ADRs, runbooks, and project docs stay searchable and consistent over time.

Who is it for?

Developers and platform engineers who store ADRs, runbooks, and technical notes in Obsidian and need systematic vault cleanup and linking.

Skip if: Teams using Confluence, Notion, or wiki-only workflows with no Obsidian markdown vault to maintain.

When should I use this skill?

A developer asks to reorganize an Obsidian vault, fix broken links, standardize tags, or refactor engineering documentation structure.

What you get

Restructured vault folders, repaired wikilinks, consistent tags, and cross-linked ADRs, runbooks, and project notes.

  • restructured vault layout
  • standardized link graph
  • tag and metadata conventions

Files

SKILL.mdMarkdownGitHub ↗

Obsidian Vault Management

Vault Structure (PARA-Based)

This vault uses a PARA-like organization:

FolderPurpose
00 - Maps of ContentIndex notes linking related topics
01 - ProjectsActive project notes
02 - AreasOngoing responsibilities
03 - ResourcesReference materials
04 - PermanentEvergreen/zettelkasten notes
05 - FleetingQuick capture notes
06 - DailyDaily notes (YYYY/MM/YYYYMMDD.md)
07 - ArchivesCompleted/inactive content
08 - booksBook notes and clippings
99 - MetaTemplates, settings
ClippingsWeb clips and imports

Quick Reference

Linking Syntax

[[Note Name]]                    # Basic wikilink
[[Note Name|Display Text]]       # Aliased link
[[Note Name#Heading]]            # Link to heading
[[Note Name#^block-id]]          # Link to block
![[Note Name]]                   # Embed note
![[image.png]]                   # Embed image
![[Note Name#Heading]]           # Embed section

Frontmatter Template

---
created: {{date:YYYY-MM-DDTHH:mm}}
updated: {{date:YYYY-MM-DDTHH:mm}}
title: "Note Title"
type: note
status: draft
tags:
  - tag1
  - tag2
aliases:
  - "Alternate Name"
cssclasses:
  - custom-class
---

Callouts

> [!note] Title
> Content

> [!warning] Important
> Warning content

> [!tip] Helpful tip
> Tip content

> [!info]+ Collapsible (open by default)
> Content

> [!danger]- Collapsed by default
> Content

Available callout types: note, abstract, info, todo, tip, success, question, warning, failure, danger, bug, example, quote

Creating Notes

Daily Note

Create in 06 - Daily/YYYY/MM/ with filename YYYYMMDD.md:

---
created: 2025-12-09T09:00
updated: 2025-12-09T09:00
title: "20251209"
type: daily-note
status: true
tags:
  - daily
  - journal
  - 2025
  - 2025-12
aliases:
  - "2025-12-09"
date_formatted: 2025-12-09
topics:
  - "[[daily]]"
  - "[[journal]]"
related:
  - "[[2025-12-08]]"
  - "[[2025-12-10]]"
cssclasses:
  - daily
---

# Daily Note - 2025-12-09

### Tasks
- [ ] Task 1

### Journal
...

### Navigation
<< [[2025-12-08]] | **Today** | [[2025-12-10]] >>

Zettelkasten Note

Create in 04 - Permanent/:

---
created: {{date}}
type: zettelkasten
tags:
  - permanent
  - topic
---

# Note Title

## Main Insight
**Key Idea**: [Main point]

## Connections
- [[Related Note 1]]
- [[Related Note 2]]

## References
- Source citation

Dataview Queries

For dataview query syntax, see references/dataview.md.

Quick examples:

LIST FROM "06 - Daily" WHERE file.cday = date(today) SORT file.ctime DESC
TABLE status, tags FROM "01 - Projects" WHERE status != "completed"

Templates

Templates location: 99 - Meta/00 - Templates/

For Templater syntax, see references/templater.md.

Common Templater variables:

<% tp.file.title %>              # Current file name
<% tp.date.now("YYYY-MM-DD") %>  # Current date
<% tp.file.cursor(1) %>          # Cursor position
<% tp.system.prompt("Question") %> # User input prompt

Installed Plugins

PluginPurpose
DataviewQuery and display data from notes
TemplaterAdvanced templates with scripting
Auto Note MoverAuto-organize notes by tags
Periodic NotesDaily/weekly/monthly notes
KanbanKanban boards in markdown
Tag WranglerBulk tag management
Table EditorMarkdown table editing
Advanced URIDeep links to notes
Local REST APIExternal API access

File Operations

Creating a Note

1. Determine appropriate folder based on note type 2. Add proper frontmatter 3. Use consistent naming conventions 4. Include relevant tags for auto-organization

Best Practices

  • Use descriptive filenames (avoid special characters except hyphens)
  • Always include created and updated timestamps
  • Tag notes for discoverability
  • Link to related notes bidirectionally
  • Use callouts for important information
  • Include navigation links in daily notes

Advanced Features

  • Dataview queries: references/dataview.md
  • Templater scripting: references/templater.md
  • Canvas diagrams: references/canvas.md
  • Plugin configurations: references/plugins.md

---

Gotchas

  • Bulk operations outside Obsidian don't trigger link-rebuilding — external scripts must signal a :Reindex or wait for the next vault open.
  • Dataview cache is per-vault and per-session — CLI script-based DQL queries may see stale state if Obsidian was last open with different filters.
  • Templater scripts via CLI run in a different context than the UI — many tp.system.* functions return nil (no UI to prompt against).
  • PARA folder moves break tag-based queries — if your queries hardcode folder paths, refactor them to use tags or properties before reorganizing.
  • Daily note rotation: changing the daily-note format mid-vault leaves old notes orphaned — they don't auto-migrate to the new format; a rename pass is needed.

Related skills

FAQ

What does obsidian-vault-management help with?

obsidian-vault-management helps developers organize, refactor, link, and maintain Obsidian vaults containing engineering notes, ADRs, runbooks, and project docs so content stays searchable and consistently structured.

Can obsidian-vault-management fix broken Obsidian links?

obsidian-vault-management supports repairing and standardizing wikilinks and cross-references across an engineering vault, reducing broken navigation between ADRs, runbooks, and project pages.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.