Create live dashboards in Obsidian
wiki-dashboardskillsetup L2★1,276
Ar9av/obsidian-wiki ↗What it does
Define live views over Obsidian vault with Bases YAML
Best for
Custom Obsidian vault dashboards when native Bases (no plugin) is available and views should filter/group by folder, tag, or property.
Inputs
- · Obsidian vault path (resolved via Config Resolution Protocol from .env or ~/.obsidian-wiki/config)
- · index.md describing vault categories and structure
- · view specification: folder, tag, category, or date range
- · property names from vault frontmatter (tags, status, updated, etc.)
Outputs
- · .base YAML file (Obsidian 1.8+ native, no plugin required)
- · global filters (optional, applied to all views)
- · formulas (optional, computed properties)
- · properties config (displayName per column)
- · summaries (optional, aggregation: Average, Sum, Max)
- · views: array of table/list/cards/map views
- · each view: name, limit, order, groupBy, filters, summaries
Requires
- · Obsidian 1.8+ (native Bases support)
- · Dataview MCP (optional, for GROUP BY / computed columns; native Bases preferred)
Preconditions
- · OBSIDIAN_VAULT_PATH resolved (via .env → ~/.obsidian-wiki/config → prompt setup)
- · index.md read to understand vault structure
- · user specifies view type (folder, tag, category, date range)
Failure modes
- · Filter syntax error: bare list instead of and:/or:/not: wrapper (parse error: 'may only have one of and/or/not keys')
- · Property name mismatch: using 'note.tags' in filters but 'tags' in order: (Obsidian rewrites inconsistently)
- · groupBy at top level instead of inside view (config rejects it)
- · Schema not read before using batch_get / batch_design (missing column types)
- · Dataview assumed without checking if installed (fails silently)
- · Vault path absolute path not resolved (relative path errors)
- · Display-name truncated or special chars not escaped
Trust signals
- · YAML schema documented (filters, formulas, properties, summaries, views)
- · Filter syntax explicit with examples and CRITICAL note on expression strings
- · Property name context table (filters vs order vs groupBy vs formulas)
- · Config Resolution Protocol named (walk up CWD for .env, ~/.obsidian-wiki/config, prompt)
- · Parser error 'may only have one of and/or/not keys' documented with solution
- · Bases vs Dataview comparison (native preferred, Dataview for GROUP BY)
- · Three basic templates: folder filter table, cards view, groupBy property