mdvs

Infer typed schemas from Markdown frontmatter and validate files.

27|2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/edochi/mdvs --skill mdvs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mdvs
Source: https://github.com/edochi/mdvs/tree/main/skills/mdvs
Command: npx skills add https://github.com/edochi/mdvs --skill mdvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Markdown directories often rely on frontmatter to describe documents, but without a centralized schema or robust validation, inconsistencies creep in and semantic search is hampered.

Core Features & Use Cases

  • Infer a typed schema from frontmatter across directories
  • Validate frontmatter against the inferred mdvs.toml
  • Perform semantic search with meaning-based retrieval and SQL-based filtering

Quick Start

Run mdvs init <path> to infer a schema and validate frontmatter for your markdown directory.

Frequently Asked Questions about mdvs

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

FAQPage Schema
How do I validate frontmatter across a directory of Markdown files?

You can validate frontmatter by running mdvs init on a directory to infer a typed schema, generating an mdvs.toml config, and then running check to validate Markdown files against the inferred rules.

Can I perform semantic search within my Markdown notes vault?

Yes, you can perform semantic search within a Markdown vault by running build to index the directory for meaning-based retrieval, followed by search to query documents with SQL-based filtering.

What is the best way to infer a schema from existing Markdown frontmatter?

Inferring a schema from Markdown frontmatter is best handled by running the init command, which analyzes existing files to generate a centralized mdvs.toml configuration for validation.

How do I incrementally update Markdown frontmatter validation rules?

You can incrementally update validation rules by modifying the mdvs.toml file and running the update command, which applies the new schema rules and stores artifacts in the .mdvs/ directory.

Does this Markdown validation tool support nested subdirectories?

Yes, the validation and semantic search mechanisms apply to any directory of Markdown files, enabling schema inference and validation across and within nested subdirectories.

Why does my Markdown vault need a schema for frontmatter?

A schema is needed to prevent inconsistencies in frontmatter across Markdown files, enabling robust validation and meaning-based semantic search that would otherwise be hampered by decentralized data.