obsidian-vault-ops

Read and write Obsidian vault files, manage wiki-links, process markdown with YAML frontmatter. Use when working with vault file operations, creating notes, or managing links.

Quality

86%

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

72%

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

The body is well-organized and token-efficient with concrete reference examples, but the procedural workflows rely on prose and vague direction instead of executable specifics and omit validation checkpoints for destructive file writes.

Suggestions

Replace vague procedural bullets ('Use appropriate template if available', 'Apply standard tag format', 'Suggest wiki-links to related notes') with concrete, executable guidance — e.g., exact Glob/Grep patterns for Finding Related Notes and explicit Edit/Write calls with paths for Creating Notes.

Add validation/verification checkpoints to write workflows — e.g., re-read the written Daily Note to confirm frontmatter parses and wiki-links resolve, with a fix-and-retry loop — since overwriting vault files is destructive.

Tighten 'Best Practices' by converting generic advice ('Preserve existing structure', 'Use relative paths') into specific rules, or move it to a reference file so the overview stays lean.

Dimension	Reasoning	Score
Conciseness	The body is lean — bullet points and code blocks with no padding explaining concepts Claude already knows (no 'what is Obsidian' preamble), and every section adds vault-specific information.	3 / 3
Actionability	Strong concrete reference examples (wiki-link format, YAML frontmatter, template variables, tag formats) but procedural guidance is prose without executable commands and includes vague bullets like 'Use appropriate template if available' and 'Apply standard tag format'.	2 / 3
Workflow Clarity	Daily Note Creation and Finding Related Notes provide clear numbered sequences, but file-write workflows lack explicit validation/verification checkpoints or error-recovery feedback loops, capping the score per the destructive-operations guideline.	2 / 3
Progressive Disclosure	Single-file skill with no bundle files; content is well-organized into clearly headed sections with no nested or deeply chained references.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 concise, third-person, and names concrete capabilities with an explicit 'Use when' trigger clause covering both what and when. It is clearly distinguishable from generic file or markdown skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Read and write Obsidian vault files, manage wiki-links, process markdown with YAML frontmatter' — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Explicitly answers both 'what' (read/write files, manage wiki-links, process markdown) and 'when' via an explicit 'Use when working with vault file operations, creating notes, or managing links' trigger clause.	3 / 3
Trigger Term Quality	Covers natural user terms — 'Obsidian vault files', 'wiki-links', 'creating notes', 'managing links' — that a user would naturally say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to the Obsidian-vault niche with distinct triggers, making it unlikely to fire for unrelated file or markdown skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: ballred/obsidian-claude-pkm
Path: vault-template/.claude/skills/obsidian-vault-ops/SKILL.md
Commit: ef1e4da

Reviewed: about 2 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.