obsidian-vault-manager

Create, organize, and maintain Obsidian vault notes, folders, and links; manage templates, daily notes, and vault structure via the Obsidian Local REST API or filesystem.

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/obsidian-vault-manager/SKILL.md

Quality

Content

53%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 body is well-structured and token-efficient but lacks concrete executable guidance — no API call examples or commands — and has no validation checkpoint in a workflow that performs destructive operations. These gaps hold actionability and workflow clarity down.

Suggestions

Add concrete executable examples for the common cases, e.g. sample REST API calls (curl/httpie) against port 27123 for note CRUD and search, or explicit filesystem path conventions, to lift actionability.

Insert a validation/verification step in the workflow (e.g. 'Verify the note was created and wikilinks resolve before logging') so destructive and batch operations clear the workflow-clarity cap.

Add a local reference file such as references/api-endpoints.md documenting the Obsidian Local REST API endpoint catalog and link to it from the MCP section, improving both actionability and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence without explaining what Obsidian is; the only minor trim candidate is the eight Invocation examples that partially overlap the description, keeping it just below 5.	4 / 5
Actionability	Guidance is high-level ('Perform requested operation — create, read, update, delete, search, or list') with no executable code or API call examples; only the port 27123 and plugin URL are concrete, so it sits at minimal concrete guidance rather than fully vague.	2 / 5
Workflow Clarity	Seven workflow steps are clearly sequenced, but the workflow includes destructive (delete) and batch operations with no validation/verification checkpoint, capping workflow clarity at 3 per the rubric guideline.	3 / 5
Progressive Disclosure	Well-organized sections (Purpose, Invocation, Workflow, Safety, MCP, References, Companion Skills) in a compact single file with easy navigation; not 5 because the REST API endpoint catalog that would warrant a local reference file is absent rather than split out.	4 / 5
	Total	13 / 20 Passed

Description

71%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 specific and clearly scoped to Obsidian vault management with good natural trigger terms, but it omits any explicit 'Use when...' guidance, capping completeness. Adding a trigger clause and markdown synonyms would raise the score.

Suggestions

Add an explicit trigger clause, e.g. 'Use when managing an Obsidian vault — creating or editing notes, daily notes, templates, folders, or backlinks' to answer the 'when' and lift completeness above 3.

Include natural synonyms and file extensions such as 'markdown notes' or '.md files' to round out trigger term coverage toward 5.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across several objects — 'Create, organize, and maintain Obsidian vault notes, folders, and links; manage templates, daily notes, and vault structure' — giving comprehensive coverage; not the 4 anchor because no meaningful coverage gap remains.	5 / 5
Completeness	The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('vault notes, folders, links, templates, daily notes') users would actually say, but missing synonyms and file extensions like '.md' or 'markdown' that the 5 anchor requires.	4 / 5
Distinctiveness Conflict Risk	The Obsidian-vault niche ('via the Obsidian Local REST API or filesystem') is clearly distinct, but companion skills that also write to the vault create minor overlap risk, keeping it just below 5.	4 / 5
	Total	16 / 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: pvnkmnk/AgenticSelfHostSkills
Path: skills/obsidian-vault-manager/SKILL.md
Commit: 0f62e6b

Reviewed: 4 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.