obsidian

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

2.12x

Quality

76%

Does it follow best practices?

Impact

100%

2.12x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/obsidian/SKILL.md

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

Quality

Content

87%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 concise, actionable, and well-structured with executable commands throughout. The main gap is the absence of validation/verification steps around the destructive delete and move-refactor operations, which caps workflow clarity.

Suggestions

Add a verification step before `obsidian-cli delete`, e.g. confirm the note exists with `search` and show the path before deletion.

For `move`, add a post-check (re-run `search` or verify wikilinks resolved) to confirm the refactor succeeded before considering it done.

Add a brief note on how to verify a created note opened correctly when the URI handler is involved.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence ("Obsidian vault = a normal folder on disk.") with terse bullets and commands; nearly every token earns its place and no basic concepts are over-explained.	5 / 5
Actionability	Provides copy-paste-ready commands for the common cases (print-default --path-only, search, search-content, create --content --open, move, delete) with exact flags and argument shapes.	5 / 5
Workflow Clarity	Sections are sequenced (find vault -> quick start -> search/create/move/delete), but destructive operations (delete, move refactor) lack validation or verification steps, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed; the body is well-organized with clear section headers and bullets, giving easy navigation for a compact single-purpose skill.	5 / 5
	Total	18 / 20 Passed

Description

65%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, distinctive niche and a concrete tool, but lacks an explicit 'Use when...' trigger clause and leans on the generic verb 'Work with'. Adding trigger phrases and more concrete actions would lift completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with Obsidian vaults, searching or creating notes, or refactoring wikilinks across a vault.'

Replace the generic 'Work with' with concrete actions such as 'Search, create, move, and delete notes' to raise specificity.

Include natural synonyms and the .md extension (e.g. 'Markdown notes (.md)') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Obsidian vaults (plain Markdown notes)") plus one concrete action ("automate via obsidian-cli"), but the leading verb "Work with" is generic and coverage is not comprehensive.	3 / 5
Completeness	The 'what' is clear (work with vaults, automate via the CLI) but there is no 'Use when...' trigger clause, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users would say ("Obsidian vaults", "Markdown notes", "obsidian-cli") but omits common variations like ".md", "notes", or "linking/wikilinks".	4 / 5
Distinctiveness Conflict Risk	"Obsidian vaults" and "obsidian-cli" name a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	15 / 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: trpc-group/trpc-agent-go
Path: openclaw/skills/obsidian/SKILL.md
Commit: ba4a78e

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.