CtrlK
BlogDocsLog inGet started
Tessl Logo

obsidian

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

58

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/obsidian/SKILL.md
SKILL.md
Quality
Evals
Security

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 an efficient, actionable reference of concrete obsidian-cli commands organized into clear sections. Its main gap is the absence of validation/verification steps for the destructive move and delete operations.

Suggestions

Add a verification step after `move`, e.g. re-run `search` to confirm the note exists at the new path and that wikilinks resolve.

Add a guardrail before `delete`, e.g. confirm the note path with `search` first or note that deletion is irreversible.

Optionally show how to verify the default vault path resolved correctly (e.g. echo `print-default --path-only`) before running batch operations.

DimensionReasoningScore

Conciseness

The body is lean and terse: "Obsidian vault = a normal folder on disk." plus compact command lists, with no padding or explanations of concepts Claude already knows.

3 / 3

Actionability

Provides concrete, copy-paste-ready commands (search-content, create --content --open, move, delete) plus the exact config path; copy-paste ready.

3 / 3

Workflow Clarity

Sections are sequenced (find vault -> quick start -> search/create/move/delete), but destructive move/delete operations lack validation or verification checkpoints, which caps this at 2.

2 / 3

Progressive Disclosure

Under 50 lines with no external references needed; content is well-organized into clear navigable sections (vault structure, find active vault, CLI quick start).

3 / 3

Total

11

/

12

Passed

Description

50%

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 clear domain and tool but relies on vague verbs ("work with", "automate") and omits any explicit "Use when..." trigger guidance. It is competent but underdeveloped versus the rubric's top anchors.

Suggestions

Replace generic verbs with specific actions, e.g. "Search, create, move, rename, and delete notes in Obsidian vaults via obsidian-cli."

Add an explicit trigger clause, e.g. "Use when the user asks to manage, search, or refactor Obsidian notes or mentions vaults/wikilinks."

Include natural trigger variations users say (notes, wikilinks, backlinks, vault) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ("Obsidian vaults", "plain Markdown notes") and a concrete tool ("automate via obsidian-cli"), but the verbs "work with" and "automate" are generic rather than listing multiple specific actions.

2 / 3

Completeness

States what the skill does but has no "Use when..." trigger clause, so the "when" is missing; the missing trigger guidance caps this at 2.

2 / 3

Trigger Term Quality

Includes natural user terms like "Obsidian vaults" and "plain Markdown notes", but lacks common variations users would mention (e.g., notes, wikilinks, backlinks).

2 / 3

Distinctiveness Conflict Risk

The Obsidian/obsidian-cli framing is a clear niche and unlikely to conflict, but the generic "work with Markdown notes" could still overlap with general Markdown skills.

2 / 3

Total

8

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.