obsidian-bases

To create an Obsidian Base, you define a .base YAML file specifying views like table or cards, then apply global and per-view filters on note properties such as tags or file metadata to display dynamic content.

Obsidian Bases are YAML-based .base files that define dynamic, reusable views of notes across a vault. You need them when building table, cards, list, or map views with global filters, formulas, and summaries for standardized reporting.

Yes, you can embed Obsidian Bases inside Markdown notes. The .base files include specific instructions for embedding within Markdown, allowing you to reuse standardized views across multiple vault files.

You configure multiple views in a single .base file by defining each view type—such as table, cards, list, or map—within the YAML schema, then setting per-view properties, filters, and summaries independently for each view.

The best way to apply formulas and summaries across Obsidian notes is by configuring them within a .base file. The YAML schema supports formulas and summary configurations applied globally or scoped to individual dynamic views.

Yes, the Obsidian Bases skill works without external dependencies. It relies entirely on the YAML-based .base file schema native to Obsidian, requiring no additional components or plugins to generate views and filters.