wiki-dashboard

Create dynamic, queryable dashboard views of the Obsidian vault using Obsidian Bases or Dataview. Use this skill when the user says "create a dashboard", "vault dashboard", "show all X as a table", "dynamic view", "query my vault", "build a content index", "show me all concepts/entities/projects", or wants a structured, auto-updating view of their wiki content. Bases is native to Obsidian 1.8+ (no plugin needed). Dataview requires the community plugin.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill body with executable examples and validation checkpoints, but it carries significant length and repetition across its Bases examples and keeps reference-style material inline rather than in bundled files. The weakest dimensions are conciseness and progressive disclosure.

Suggestions

Consolidate the seven Bases YAML examples into 2-3 canonical ones (e.g., a basic table and a groupBy example) and rely on the property-name and filter-expression reference tables for the rest, cutting repeated scaffolding.

Move the Bases recipe catalog and the Dataview reference into separate bundled reference files (e.g., references/bases-recipes.md, references/dataview-queries.md) with clearly signaled links from SKILL.md to improve progressive disclosure.

Fix the workflow numbering so the build step is explicitly labeled 'Step 1/2' before 'Step 3: Write the File', removing the confusing gap in the step sequence.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but is noticeably long — seven near-identical Bases YAML examples (basic table, cards, group by, tag filter, multi-filter, OR filter, computed column) repeat the properties/views scaffolding and could be consolidated into a couple of canonical examples plus the reference tables.	3 / 5
Actionability	It provides complete, copy-paste-ready YAML schemas, Dataview query blocks, concrete file paths ($OBSIDIAN_VAULT_PATH/_meta/...), slug examples, and bash commands, covering the common dashboard cases fully.	5 / 5
Workflow Clarity	There is a clear sequenced flow (Before You Start → Option A/B → write → embed → update tracking) with a Quality Checklist and QMD error-handling feedback loop, but the section numbering jumps straight to 'Step 3' with no labeled Step 1/2, a minor sequencing gap.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is ~470 lines, so the simple-skill exception does not apply; the filter-expression and Dataview reference tables and the full recipe catalog are inlined in SKILL.md rather than split into separate reference files, though the one external pointer (llm-wiki/SKILL.md) is clearly signaled.	3 / 5
	Total	15 / 20 Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly covers both what the skill does and when to use it, with comprehensive natural trigger phrases and a clear, low-conflict niche. The only softer dimension is specificity, which names one main action rather than a list of several distinct operations.

Dimension	Reasoning	Score
Specificity	It names the domain (Obsidian vault) and two tools (Bases, Dataview) with one concrete action — 'Create dynamic, queryable dashboard views' — but does not enumerate multiple distinct actions, fitting the anchor for naming a domain with 1-2 concrete actions rather than several.	3 / 5
Completeness	It explicitly states both what ('Create dynamic, queryable dashboard views of the Obsidian vault using Obsidian Bases or Dataview') and when ('Use this skill when the user says...'), with concrete trigger phrases, matching the anchor for clearly answering both.	5 / 5
Trigger Term Quality	It packs in natural user phrases — 'create a dashboard', 'vault dashboard', 'show all X as a table', 'dynamic view', 'query my vault', 'build a content index', 'show me all concepts/entities/projects' — giving comprehensive coverage of the terms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The Obsidian-vault / Bases / Dataview niche with vault-specific trigger phrases ('vault dashboard', 'query my vault') is clearly distinct from other skills with minimal overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Ar9av/obsidian-wiki
Path: .skills/wiki-dashboard/SKILL.md
Commit: 52c9f2b

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.