vault-librarian

Automate PARA filing and living-document maintenance for Obsidian vaults.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/JSai23/claude-tooling --skill vault-librarian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-librarian
Source: https://github.com/JSai23/claude-tooling/tree/main/compiled/vault/agentskills/vault-librarian
Command: npx skills add https://github.com/JSai23/claude-tooling --skill vault-librarian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the organization of raw captures into a clean, navigable Obsidian vault by enforcing PARA filing, updating living documents, and maintaining backlinks and tags.

Core Features & Use Cases

  • Process inbox items: read intent, file to the correct PARA destinations, and update living docs.
  • Maintain living documents (MOCs and project briefs) as notes are filed, including cross-links and backlinks.
  • Audit and enforce structure: run validation, tag audits, and cross-link management to ensure vault coherence.

Quick Start

Process a new inbox item by interpreting its intent, file it to the correct PARA destination, and refresh the vault's living docs.

Frequently Asked Questions about vault-librarian

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate PARA filing for my Obsidian vault inbox?

Automating PARA filing for an Obsidian vault involves interpreting the intent of new captures, moving them to correct destinations, and updating living documents. This skill enforces strict frontmatter schemas to maintain navigability.

What is the best way to maintain backlinks and tags across living documents?

Maintaining backlinks and tags across living documents requires running validation and tag audits to ensure vault coherence. This skill governs cross-link management and enforces structure as notes are filed.

How do I process an inbox item and update MOCs in Obsidian?

Processing an inbox item and updating MOCs requires reading the item intent, filing it to the correct PARA destination, and refreshing the vault's living docs. The workflow generates cross-links and backlinks automatically.

Can I enforce strict frontmatter schemas and naming conventions in my vault?

Enforcing strict frontmatter schemas and naming conventions in a vault is possible through a robust audit workflow. This skill validates structure during inbox processing and area updates to keep documents coherent.

Why does my vault lose navigability after bulk processing inbox items?

A vault loses navigability after bulk processing when living documents are not updated with new cross-links. Running a tag audit and backlink generation ensures structure remains coherent across all project and area notes.