wiki-dashboard creates queryable views over your vault so that indexes and tables stay current without manual edits. It prefers Obsidian Bases, the native YAML-based view format in Obsidian 1.8 and later, and uses the Dataview community plugin when you ask for it or need grouping and computed columns.
It carries the exact syntax rules that trip people up: expression-string filters under and, or and not, groupBy inside the view, and the rows prefix after a Dataview GROUP BY. Files are saved to a meta folder in the vault.
What You Get
- A .base file or a dashboard note saved under the vault’s meta folder with a descriptive name
- Table, cards and grouped views with column display names and computed day-count formulas
- Dataview queries for stale pages, concepts by domain and multi-folder lists
- A one-line log entry recording which dashboard was created
- Instructions for embedding a Bases file inside a note
Common Use Cases
- Building a card gallery of all entity pages
- Listing pages untouched for 30 days or more
- Showing recent ingests sorted by created date
What Makes It Unique
It documents the failure cases for both tools: a bare list of filters causes a parse error in Bases, grouping at the top level is ignored, a grouped property should be left out of the column order, and Dataview date math is safest on file modification time. A quality checklist at the end repeats those rules so each generated file can be verified before you open it.
Under The Hood
The skill is instructions for the agent. It reads the vault index, writes a .base file or Markdown note into the vault’s meta folder, and appends a line to the vault log. It asks before editing an existing note to embed a Bases file. It runs the qmd command when a QMD collection is configured. It does not fetch web pages or call remote APIs, and the Dataview or Bases engine inside Obsidian runs the queries.