obsidian-vault

Organize Obsidian vaults with MOCs, wikilinks, frontmatter/properties, dashboards, orphan-note checks, and cleanup workflows. Use ONLY when the user explicitly refers to Obsidian — by naming "Obsidian", an Obsidian "vault", or an Obsidian-specific feature such as wikilinks ("[[ ]]"), the Dataview or Bases plugins, or Obsidian Properties. Within that Obsidian context it covers creating Maps of Content, adding/fixing wikilinks, finding orphan notes, normalizing YAML frontmatter, generating Dataview/Bases dashboards, organizing folders, deduplicating or renaming notes, and preparing the vault for AI use. Do NOT use this skill for generic note-taking, Markdown, or knowledge-base requests that don't mention Obsidian.

Quality

93%

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

86%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.

The content is dense, actionable, and well-structured, with executable templates, specific commands, sequenced workflows, and a finishing checklist that includes validation for destructive operations. The only meaningful gap is minor conciseness trimming and a few implicit rather than explicit validation checkpoints.

Suggestions

Tighten the opening 'Obsidian-specific facts' block and replace example dates ('2026-06-18') with placeholders to reduce time-sensitive padding.

Make the destructive-operation validation explicit with validate-fix-retry language (e.g. after repointing links, re-run start_search to confirm zero inbound links before deleting the discarded note).

Move the 'Bases is built in since Obsidian 1.9' version note into a clearly labeled version/compatibility aside so it does not read as ambient detail.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes competence, but a few sentences restate basics and example dates (e.g. 'updated: 2026-06-18') and the 'Bases is built in since Obsidian 1.9' note add minor time-sensitive padding; not quite the fully trimmed level-5 example.	4 / 5
Actionability	Provides copy-paste-ready Dataview queries, a YAML frontmatter template, a MOC template, and concrete tool commands ('start_search', 'edit_block', 'write_file', 'read_multiple_files') covering the common cases.	5 / 5
Workflow Clarity	The Workflows section, the numbered orphan-remediation procedure, and the 'Checklist before finishing' give a clear sequence with validation for destructive/batch ops (repoint inbound links before deleting; moves inside Obsidian), but a couple of checkpoints are implicit rather than explicit validate-fix-retry loops.	4 / 5
Progressive Disclosure	The skill is a single well-organized SKILL.md with clear section headers and no need for external bundle references (none exist), which meets the rubric's exception that well-organized content with no external-reference need can score 5.	5 / 5
	Total	18 / 20 Passed

Description

100%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.

The description is a strong example: it states a comprehensive set of concrete capabilities, gives explicit positive and negative trigger guidance using natural user terms and Obsidian-specific feature names, and is written in third person. It clearly and concisely answers both what the skill does and when to use it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating Maps of Content, adding/fixing wikilinks, finding orphan notes, normalizing YAML frontmatter, generating Dataview/Bases dashboards, organizing folders, deduplicating or renaming notes' — giving comprehensive coverage rather than vague abstractions.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated capabilities) and 'when' ("Use ONLY when the user explicitly refers to Obsidian — by naming 'Obsidian', an Obsidian 'vault', or an Obsidian-specific feature") with concrete trigger phrases and a negative boundary.	5 / 5
Trigger Term Quality	Covers natural user terms including synonyms and feature-specific triggers: 'Obsidian', 'vault', "wikilinks ('[[ ]]')", 'Dataview', 'Bases', and 'Obsidian Properties'.	5 / 5
Distinctiveness Conflict Risk	The 'Use ONLY when' gating plus "Do NOT use this skill for generic note-taking, Markdown, or knowledge-base requests that don't mention Obsidian" carves a clear niche with minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: wonderwhy-er/DesktopCommanderMCP
Path: plugins/claude/skills/obsidian-vault/SKILL.md
Commit: 9bd8422

Reviewed: 8 days 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.