obsidian

Use this skill whenever the user wants to work with Obsidian in any capacity. This is the ONLY skill for Obsidian vaults, .base files, Obsidian Markdown, Obsidian plugins, and Obsidian Web Clipper. Trigger for: creating or editing notes with wikilinks, callouts, embeds, or frontmatter; building or debugging .base files (formulas, filters, views, YAML quoting); Obsidian plugin development or hot-reload; Web Clipper JSON templates or AI Interpreter prompts; vault structure, daily notes, or the obsidian CLI. Also trigger when the user describes Obsidian-specific problems without naming Obsidian — like .base YAML errors, foldable callout syntax, base formula for tasks due this week, or clipper template for arxiv. Do NOT trigger for Logseq, Notion, Dataview plugin queries, generic markdown processing scripts, or general-purpose Chrome extensions.

Quality

92%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, comprehensive Obsidian skill that covers four distinct domains with clear workflows, concrete examples, and excellent progressive disclosure to reference files. The actionability is strong with copy-paste ready syntax throughout and explicit validation/troubleshooting guidance. The main weakness is moderate verbosity — some content (file properties table, standard markdown mentions, explanatory phrases) could be tightened to save tokens without losing clarity.

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some content Claude already knows (standard markdown syntax mentions, explanations of what tags are, what YAML is). The file properties table and some inline examples could be more tightly written, though most Obsidian-specific syntax genuinely adds value since it's non-standard.	2 / 3
Actionability	The skill provides concrete, copy-paste ready syntax examples throughout — wikilink formats, .base YAML schemas, CLI commands, filter syntax, formula examples with correct/incorrect patterns, and complete note examples. The Web Clipper section includes specific verification rules and output format requirements.	3 / 3
Workflow Clarity	Each domain has a clearly sequenced workflow with validation checkpoints. The Bases workflow includes explicit validation steps (step 5: verify YAML, check properties exist, common issues listed) and a test step. The Web Clipper workflow has a required fetch-and-verify step with explicit rules about never guessing selectors. The plugin dev workflow sequences reload → check errors → verify visually.	3 / 3
Progressive Disclosure	Excellent structure with a clear domain table at the top, concise inline essentials for each domain, and well-signaled one-level-deep references to detailed files (bases-functions.md, clipper-variables.md, clipper-filters.md, etc.). The skill serves as a navigable overview without burying critical details in nested references.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that thoroughly covers what the skill does, when to trigger it, and importantly when NOT to trigger it. It provides rich natural trigger terms covering both explicit Obsidian mentions and implicit Obsidian-related problems. The negative trigger list is a strong addition that minimizes conflict risk with adjacent skills. One minor note: it uses second person ('Use this skill') at the start, but since it's addressed to Claude as the agent selecting skills rather than to a user, this is a borderline case.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: creating/editing notes with wikilinks, callouts, embeds, frontmatter; building/debugging .base files with formulas, filters, views; plugin development with hot-reload; Web Clipper JSON templates; vault structure; daily notes; CLI usage.	3 / 3
Completeness	Clearly answers both 'what' (work with Obsidian vaults, .base files, plugins, Web Clipper, notes with various Obsidian-specific features) and 'when' with explicit trigger guidance ('Trigger for:', 'Also trigger when...', 'Do NOT trigger for...'). The when clause is exceptionally detailed with both positive and negative trigger conditions.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms including 'Obsidian', 'wikilinks', 'callouts', 'embeds', 'frontmatter', '.base files', 'hot-reload', 'Web Clipper', 'daily notes', 'obsidian CLI', 'foldable callout syntax', 'base formula', 'clipper template', and even implicit triggers like '.base YAML errors'. Also includes negative triggers to avoid false matches.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with explicit negative boundaries excluding Logseq, Notion, Dataview plugin queries, generic markdown processing, and general Chrome extensions. The description carves out a very clear niche for Obsidian-specific work and even addresses edge cases where users might describe Obsidian problems without naming Obsidian.	3 / 3
	Total	12 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: seanGSISG/claude-depot
Commit: 48bf6a4

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