obsidian

Obsidian vault: search/read/write notes, backlinks, Bases, Canvas.

Quality

73%

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/SKILL.md

Quality

Content

76%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 highly actionable with concrete, copy-paste commands and good section organization, but workflows involving destructive writes lack explicit validation/feedback checkpoints. It is concise but has minor over-explanation.

Suggestions

Add explicit validation checkpoints for destructive operations, e.g. after `obsidian move` verify links updated, and confirm a note exists before delete/trash.

Add a feedback loop for JSON edits (validate `.base`/`.canvas`/`.json` after editing) to lift workflow clarity.

Trim the structural aside 'An Obsidian vault is a normal folder of Markdown files plus `.obsidian/` config' or fold it into the Sources list to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with grouped commands and minimal prose; "An Obsidian vault is a normal folder of Markdown files plus `.obsidian/` config" is a minor instance of over-explanation, keeping it at anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	Concrete copy-paste commands cover common cases across read, write, bases, and canvas (e.g. `obsidian search query=...`, `obsidian read path=...`, `apply_patch`, `sed -n`), matching the fully executable anchor 5.	5 / 5
Workflow Clarity	Workflows are sequenced into clear sections, but destructive/batch operations (move, delete, bulk edits) lack explicit validation checkpoints; per rubric guidance this caps workflow clarity at anchor 3.	3 / 5
Progressive Disclosure	The skill is self-contained with well-organized sections and no external bundle files; at ~107 lines it exceeds the under-50-line simple-skill exception, so it sits at anchor 4 (good structure, no references needed) rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

70%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 well-scoped to Obsidian vault work with strong distinctiveness, but it omits any explicit 'Use when...' trigger guidance, which caps completeness. It is terse but could benefit from natural-language trigger phrases.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with an Obsidian vault or when the user mentions notes, backlinks, Bases, Canvas, or .md files.'

Include common synonyms and file extensions (markdown, .md, wikilinks, daily notes, plugins) to broaden natural trigger coverage.

Expand the action list slightly (e.g. daily notes, plugins, properties) to move toward comprehensive capability coverage.

Dimension	Reasoning	Score
Specificity	"search/read/write notes, backlinks, Bases, Canvas" lists several concrete capabilities with minor gaps (no daily notes, plugins, properties), matching anchor 4 rather than the comprehensive anchor 5.	4 / 5
Completeness	The description gives a clear 'what' (search/read/write notes, backlinks, Bases, Canvas) but no 'Use when...' trigger clause; per rubric guidance a missing explicit trigger caps completeness at anchor 3.	3 / 5
Trigger Term Quality	"Obsidian vault", "notes", "backlinks", "Bases", "Canvas" are natural user terms with good coverage, but synonyms (markdown, .md, wikilinks, daily notes, plugins) are missing, so it fits anchor 4 not anchor 5.	4 / 5
Distinctiveness Conflict Risk	"Obsidian vault" names a clear niche with distinct triggers and minimal conflict risk, matching the anchor 5 example of a well-scoped domain.	5 / 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: steipete/agent-scripts
Path: skills/obsidian/SKILL.md
Commit: 2b082d9

Reviewed: 1 day 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.