obsidian-bases is a compact workflow and syntax reference for Obsidian Bases, the database-like views over note properties. It helps Claude choose a minimal filter, add formulas only where a value must be computed, pick a view type, and validate YAML quoting and property names.
Questions are answered read-only. When you ask for a .base edit, the full file and its expected result set are previewed and written through one inspected transaction.
What You Get
- A drafted .base file with a minimal filter and only the formulas that are needed
- Validation of YAML, expression quoting, formula references and null handling
- Table, cards, list or kanban view definitions with version notes
- A preview of the whole file and the expected result set before any write
- Embed syntax for a Base or a single named view inside a note
Common Use Cases
- Building a reading list or task tracker as a card or kanban view
- Adding a computed status column with a guarded formula
- Fixing a broken .base file after a quoting or property-name mistake
What Makes It Unique
It prefers the upstream kepano obsidian-bases skill and the official docs for fine detail, and acts as a compact fallback. It records static validation separately from what Obsidian rendered, warns against Dataview-only keys such as from and where, and preserves unknown view fields on older apps.
Under The Hood
The skill is instructions plus inline examples. Syntax questions need no tools. For a requested edit it runs the plugin’s Python core script through the shell to inspect and apply a transaction bundle, and only .base files under wiki/ are written, after you approve the plan hash. It does not fetch web pages. It points to a conformance procedure in the repository for behavior that cannot be checked offline.