obsidian

Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.

Quality

72%

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

The canonical home for this skill is obsidian in Hung-Reo/hungreo-openclaw

Quality

Content

83%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 a tight, highly actionable CLI command reference that respects the context budget. Its main weakness is the absence of validation/verification steps around destructive operations like delete and move.

Suggestions

Add a verification checkpoint before destructive ops, e.g. run 'obsidian-cli search' to confirm the target note exists before 'delete', and warn that delete is irreversible.

For 'move', note how to verify wikilinks were updated (e.g. re-run search-content for the old path) so the refactor can be validated.

Consider splitting the CLI command catalog into a references file once the skill grows, keeping SKILL.md as a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — it jumps to concrete commands and vault-structure facts Claude would not already know, with no padding about what Obsidian is.	5 / 5
Actionability	It provides copy-paste-ready commands for every common case (search, search-content, create, move, delete, print-default), with exact flags and arguments.	5 / 5
Workflow Clarity	Commands are well grouped, but destructive operations like 'obsidian-cli delete' and 'move' have no validation or verification checkpoints, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is well organized under clear section headers with no nested references, but there are no bundle files or one-level-deep references to demonstrate progressive disclosure, and it sits just over the 50-line simple-skill threshold.	4 / 5
	Total	17 / 20 Passed

Description

61%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 names a specific tool and domain clearly but omits any explicit 'when to use' guidance, which limits its completeness and trigger clarity. It is reasonably distinct but slightly broadened by the generic markdown framing.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks to search, create, move, or delete Obsidian notes, or mentions vaults, wikilinks, or .md notes.'

Replace the generic 'Work with' verb with the specific actions the skill performs (search, create, move/rename, delete notes) to lift specificity.

Include natural synonyms and file extensions (e.g. 'Obsidian notes', 'wikilinks', '.md') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'automate via obsidian-cli' names a concrete tool, and 'Work with Obsidian vaults' names the domain, but 'Work with' is generic and coverage is not comprehensive.	3 / 5
Completeness	It states a clear 'what' (work with vaults, automate via CLI) but provides no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	'Obsidian vaults' and 'plain Markdown notes' are natural terms users would say, though common variations like '.md' or 'wikilinks' are missing.	4 / 5
Distinctiveness Conflict Risk	The Obsidian vault niche via obsidian-cli is mostly distinct, though the '(plain Markdown notes)' parenthetical creates minor overlap risk with general markdown skills.	4 / 5
	Total	14 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: Bitterbot-AI/bitterbot-desktop
Path: skills/obsidian/SKILL.md
Commit: 017761f

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