CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-obsidian

Command-line interface for Obsidian — Knowledge management and note-taking via Obsidian Local REST API. Designed for AI agents and power users who need to manage notes, search the vault, and execute commands without the GUI.

Quality

72%

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 ./obsidian/agent-harness/cli_anything/obsidian/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 excels at actionability with fully executable, copy-paste-ready commands and a sensible section layout, but it is held back by duplicated content, no validation guidance for destructive vault operations, and dangling references to package documentation that is not part of the skill bundle. It reads as solid CLI reference documentation rather than a tightly token-efficient skill file.

Suggestions

Add validation guidance before destructive commands, e.g. read the note with `vault read` and confirm the path with `vault list` before `vault delete` or `vault update`.

Deduplicate the repeated content: merge the two REPL sections, remove the redundant `vault list` demonstrations, drop the verbatim description repeat, and move the version number out of the skill body.

Either move the command-group tables and extended examples into a bundled reference file (e.g. references/commands.md) with a clear pointer, or remove the 'More Information' section that references README.md, TEST.md, and HARNESS.md files not present in the skill directory.

DimensionReasoningScore

Conciseness

The body is mostly efficient (command tables, terse examples) but contains clear redundancy: REPL mode is explained in two separate sections, `vault list` is demonstrated three times, the intro repeats the frontmatter description verbatim, and a bare "1.1.0" version number occupies its own section — all could be trimmed, matching the 'mostly efficient but could be tightened' anchor.

3 / 5

Actionability

Commands are fully executable and copy-paste ready, covering the common cases: `vault create "Projects/new-project.md" --content "..."`, `search query --type jsonlogic '{"==":[...]}'`, API key configuration via flag and environment variable, and the `--json` output mode, which matches the top anchor.

5 / 5

Workflow Clarity

The 'For AI Agents' section provides a numbered sequence with checkpoints (verify `server status` first, check return codes, parse stderr), but destructive operations (`vault delete`, `vault update` which overwrites) have no validation or verification guidance, which caps workflow clarity at 3 per the scoring guidelines.

3 / 5

Progressive Disclosure

Section headers and command tables give the body reasonable structure, but everything is inlined in a ~230-line file with no bundle reference files, and the 'More Information' pointers (README.md, TEST.md, HARNESS.md "in the package") are not files in the skill bundle, so navigation leads nowhere — matching 'references present but not clearly signaled; content that should be separate is inline'.

3 / 5

Total

14

/

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 is distinctive and reasonably specific with good natural keywords, but it lacks an explicit 'Use when...' trigger clause and describes capabilities at a summary level ("manage notes") rather than naming the concrete operations the CLI supports. Adding explicit trigger conditions and concrete verbs would raise both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Obsidian, their vault, or wants to manage notes from the command line."

Replace the generic phrase "manage notes" with the concrete operations the CLI supports, such as "create, read, update, append, and delete notes".

Include natural variations users might say (markdown notes, .md files, daily notes) to broaden trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain and several actions ("manage notes, search the vault, and execute commands"), but "manage notes" is a summary-level verb rather than concrete operations like create, read, append, or delete, so coverage is not comprehensive as required for anchor 4-5.

3 / 5

Completeness

The 'what' is clear (CLI for Obsidian via Local REST API), but there is no 'Use when...' clause or equivalent trigger guidance; "Designed for AI agents and power users" states the audience rather than when to use the skill, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("Obsidian", "notes", "vault", "search", "note-taking", "knowledge management", "command-line") that users would actually say, though common variations like markdown, .md, or daily notes are missing, keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Obsidian Local REST API" carves out a clear niche with distinct trigger terms (Obsidian, vault, notes), so the risk of triggering for the wrong skill is minimal.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

HKUDS/CLI-Anything

Path

obsidian/agent-harness/cli_anything/obsidian/skills/SKILL.md

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.