vault-sync

Validate Markdown frontmatter and wiki-link integrity in Obsidian vaults.

50|7|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Kanevry/session-orchestrator --skill vault-sync-kanevry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-sync
Source: https://github.com/Kanevry/session-orchestrator/tree/main/skills/vault-sync
Command: npx skills add https://github.com/Kanevry/session-orchestrator --skill vault-sync-kanevry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, zod.

What problem does it solve?

Ensures a project's markdown vault maintains strict YAML frontmatter conformity and intact wiki-style links so that both human readers and retrieval agents are not misled by broken metadata or dangling references.

Core Features & Use Cases

  • Frontmatter validation: Validates required fields and formats (id, type, created, updated, tags, expires) against a vendored Zod schema.
  • Wiki-link integrity checks: Detects dangling [[wiki-links]] and reports them as warnings so navigation and graph traversal remain reliable.
  • Operational gating: Runs as a session-end hard gate or in warn/off modes, emits machine-readable JSON reports, and returns meaningful exit codes for automation.
  • Use case: Automatically block session close when a vault file violates the schema or introduces broken links, and surface warnings for expired notes during evolve audits.

Quick Start

Run the validator wrapper pointing VAULT_DIR at your vault to generate a JSON report and an exit code indicating validity.

Frequently Asked Questions about vault-sync

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

FAQPage Schema
How do I validate Obsidian vault frontmatter and check for broken wiki-links?

You validate Obsidian vault frontmatter and wiki-links by running a Node.js validator using zod and yaml to check required fields and detect dangling references. The validator analyzes your vault directory and produces a machine-readable JSON report with meaningful exit codes.

What is frontmatter schema validation for a markdown vault?

Frontmatter schema validation for a markdown vault is the process of checking YAML metadata fields like id, type, created, updated, tags, and expires against a vendored Zod schema. This ensures strict conformity so human readers and retrieval agents are not misled by broken metadata.

How do I block a session close when a vault file violates the schema or introduces broken links?

You block a session close when a vault file violates the schema by running the validator in hard gate mode during session-end. It returns meaningful exit codes for automation, stopping the process if schema violations or dangling wiki-links are detected.

Can I exclude specific files or directories from vault validation?

Yes, you can exclude specific files from vault validation by passing exclude glob patterns to the validator. This allows you to skip excluded files and focus the schema and wiki-link integrity checks on the relevant parts of your project vault.

Does the vault validator support warn and off modes for evolve scans?

Yes, the vault validator supports hard, warn, and off modes for evolve scans. In warn mode, it surfaces warnings for expired notes and dangling links without blocking operations, while off mode disables the checks entirely.

What dependencies do I need to run vault frontmatter and wiki-link validation?

You need Node.js along with the yaml and zod dependencies to run vault frontmatter and wiki-link validation. The validator uses zod for schema enforcement and yaml for parsing frontmatter to generate a JSON report and exit codes.