Obsidian Bases
Obsidian Bases lets you build structured database views within your vault using YAML-based .base files. Define tables, cards, or lists with custom filters, computed formulas, and aggregated summaries to organize and display your notes dynamically.
Obsidian Bases enables you to create database-like views of your notes with filters, formulas, and summaries.
AI-generated summary based on this skill's SKILL.md
Install
jackjin1997/ClawForge/obsidian-bases · repository language: Python
git clone https://github.com/jackjin1997/ClawForge
cp -r ClawForge ~/.claude/skills/obsidian-basesgenerated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What are Obsidian Bases and how do they work?
Obsidian Bases lets you build structured database views within your vault using YAML-based .base files. You define tables, cards, or lists with custom filters, computed formulas, and aggregated summaries to organize and display your notes dynamically. This transforms your flat note collection into interconnected, queryable data structures without leaving Obsidian.
How do I set up Obsidian Bases in my vault?
Obsidian Bases uses YAML-based .base files to define your database structures. Create a new .base file in your vault, configure it with your desired view type (table, card, or list), specify which notes to include via filters, and define any computed fields or aggregations. Once saved, Obsidian Bases renders your structured view automatically within the vault.
What features and capabilities does Obsidian Bases offer?
Obsidian Bases provides multiple view formats (tables, cards, lists), custom filtering to query your notes, computed formulas for derived values, and aggregated summaries for data analysis. You can organize interconnected information dynamically, apply conditional logic to your displays, and create powerful dashboards—all while keeping your data in standard Obsidian notes.
Can you provide configuration and usage examples for Obsidian Bases?
Obsidian Bases configuration examples include defining table columns mapped to note properties, setting filters to show only matching records, creating card layouts for visual browsing, and adding computed fields that calculate values from your data. Each .base file uses YAML syntax to declare these structures, making it easy to version-control and customize your database views.
How do I use Obsidian Bases for beginners?
Start by creating a simple .base file with a table view of your notes. Define basic filters to narrow your data, map note fields to table columns, and save. Obsidian Bases will render your structured view instantly. Gradually add computed fields, summaries, and alternative view types (cards, lists) as you grow comfortable with the YAML syntax and filtering options.
What are the best practices for Obsidian Bases setup?
Obsidian Bases works best when your notes have consistent metadata (YAML frontmatter). Keep filters simple at first, use meaningful computed field names, and organize .base files in a dedicated folder. Test views incrementally, leverage aggregations for summaries, and document your filter logic for team collaboration or future reference.