obsidian

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

2.12x

Quality

—

Does it follow best practices?

Impact

100%

2.12x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

87%

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 concise, highly actionable command reference that assumes Claude's competence. Its only gap is the absence of validation/verification steps for the destructive move and delete operations.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with no padding or over-explanation of concepts Claude already knows (e.g. "Obsidian vault = a normal folder on disk" is a useful clarifying fact); every token earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands throughout (print-default, search, search-content, create with --content/--open, move, delete) plus a concrete config file path, matching the 'fully executable commands' anchor.	3 / 3
Workflow Clarity	Operations are organized with a find-vault sequence, but destructive/batch operations like delete and the vault-wide move ('safe refactor') have no validation or verification checkpoint; per the rubric this caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files are present and none are needed; the self-contained single-purpose reference is organized into clear sections with no nested references, fitting the simple-skill carve-out for a well-organized skill.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 cleanly identifies the Obsidian niche but is generic about actions and lacks an explicit use-when trigger. It is distinguishable but would benefit from named operations and trigger guidance.

Suggestions

Add an explicit 'Use when...' clause naming user triggers (e.g., 'Use when working with Obsidian notes, vaults, wikilinks, or when the user mentions Obsidian').

Replace the vague 'Work with' with concrete actions the skill performs (e.g., 'search, create, move, and delete notes in Obsidian vaults via obsidian-cli').

Add common natural variations like 'Obsidian notes' and 'wikilinks' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Work with Obsidian vaults" and "automate via obsidian-cli" name the domain and a concrete tool, but "Work with" is vague and no multiple specific actions are listed, matching the 'names domain and some actions' anchor rather than a 1 (pure abstraction) or 3 (multiple concrete actions).	2 / 3
Completeness	The description states what the skill does but has no "Use when..." trigger guidance; per the rubric a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	"Obsidian vaults" and "plain Markdown notes" are natural user terms, but coverage misses common variations (e.g. "Obsidian notes", "notes") and "obsidian-cli" is technical jargon, fitting 'some relevant keywords but missing common variations.'	2 / 3
Distinctiveness Conflict Risk	"Obsidian vaults" tied to the named obsidian-cli tool is a clear, distinct application niche unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 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
Commit: 737835b

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