obsidian-bases

Organize Obsidian notes into structured views using YAML-based Base files.

4|1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/kryang03/Notes --skill obsidian-bases-kryang03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-bases
Source: https://github.com/kryang03/Notes/tree/main/.github/skills/obsidian-bases
Command: npx skills add https://github.com/kryang03/Notes --skill obsidian-bases-kryang03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Obsidian Bases (.base files) provide a structured way to organize and present notes as dynamic views, enabling consistent, scalable data organization across a vault.

Core Features & Use Cases

  • Define multiple views (table, cards, list) within a single base to display notes by tags, folders, or custom formulas.
  • Apply global and per-view filters, formulas, and summaries to extract insights and streamline note curation.
  • Use cases include project dashboards, reading lists, knowledge bases, and research note systems.

Quick Start

Create a Base file (.base) with a couple of views and basic filters to organize your notes.

Frequently Asked Questions about obsidian-bases

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

FAQPage Schema
How do I create dynamic views to organize Obsidian notes?

To create dynamic views for Obsidian notes, you generate a .base file with YAML schema definitions. This structured approach enables you to configure table, card, or list layouts for vault-wide knowledge management.

What are Obsidian bases and when do I need them for my vault?

Obsidian bases are structured files that organize and present notes as dynamic, reusable views. You need them for vault-wide scenarios like building project dashboards, reading lists, or research knowledge bases to ensure scalable data organization.

Can I apply multiple filters and formulas to an Obsidian notes database?

Yes, you can apply global and per-view filters and formulas to an Obsidian notes database. By defining these properties within the YAML schema of a .base file, you extract specific insights and streamline note curation across different views.

Does this approach support building dashboards and reading lists from tagged notes?

Yes, this approach fully supports building dashboards and reading lists from tagged notes. You configure multiple view types within a single base file, applying custom formulas and filters to display notes dynamically by tags or folders.

What is the best way to structure a YAML schema for Obsidian views and summaries?

The best way to structure a YAML schema for Obsidian views is to define properties, filters, formulas, and summaries directly inside a .base file. You can also specify optional asset directories for scripts and documentation to maintain structure.