Skip to content
SkillModel-led3,312 tokens in use

wiki-dashboard

Writes live, auto-updating Obsidian dashboards as native Bases files or Dataview queries, with tested syntax rules for filters, grouping and formulas.

3,792 stars on the repository MIT LicenseAr9av/obsidian-wiki · skills/wiki-dashboard
pip install obsidian-wiki
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing wiki-dashboard costs

42tokens idle
3,312tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure23/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 442

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity28
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers