CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-joplin

Command-line interface for Joplin workflows using the real joplin terminal backend

Quality

64%

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

Quality

Content

61%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 is a well-structured, largely executable reference for the harness: install, usage, output contract, command surface, and test commands are all concrete. Main weaknesses are inlined version-specific workarounds and test baselines that bloat token cost, and the absence of explicit validation checkpoints for mutating operations.

Suggestions

Add an explicit validation step after mutating commands (e.g. re-run 'notes list' or verify via the 'ok'/'error' fields before proceeding, and recommend '--dry-run' first for destructive operations).

Move version-sensitive material — the Joplin 3.6.x version-command fallback probing details and the 'Current validation baseline' test counts — into a reference file or a clearly labeled compatibility section.

Demonstrate the '--profile' flag in a usage example, since it is listed under Requirements but never shown.

DimensionReasoningScore

Conciseness

The body is mostly dense and operational, but inlines time-sensitive, version-specific detail — 'Joplin 3.6.x can have a broken version command... probing the symlink-resolved binary directory, the Windows-style sibling node_modules/joplin...' and 'Current validation baseline (Windows + Joplin CLI 3.6.2): 134 passed, 1 skipped' — which the guidelines penalize unless placed in a deprecated/reference section. Not score 4 because this version-specific material is more than a minor trim.

3 / 5

Actionability

Install, usage (REPL, one-shot, stateful project, dry-run), and test commands are concrete and copy-paste executable, covering the common cases. Not score 5 due to minor gaps: '--profile' is mentioned in Requirements but never demonstrated, and arguments for most command groups (todos, tags, sync, e2ee, etc.) are unspecified.

4 / 5

Workflow Clarity

Usage patterns imply a sequence (project new -> notes create -> save) and the JSON error contract plus '--dry-run' provide implicit safety, but there is no explicit validate-after-mutation checkpoint for destructive/batch operations ('remove', sync, import/export), which caps workflow clarity at 3 per the rubric guidelines. Not score 2 because sequences, error handling, and dry-run guidance are present.

3 / 5

Progressive Disclosure

The body is well-organized into clear sections (Requirements, Install, Usage, JSON output contract, Command groups, Agent guidance, Test workflow) with no bundle files to reference. Not score 5 because at ~105 lines, content like the full command-group listing and test baselines could be split into a reference file rather than inlined.

4 / 5

Total

14

/

20

Passed

Description

48%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 identifies a clear, distinctive niche (Joplin CLI automation via the real terminal backend) but is underspecified: it enumerates no concrete actions, includes few natural trigger terms, and omits any 'when to use' guidance. It reads as a domain label rather than a capability description.

Suggestions

Enumerate concrete capabilities in the description, e.g. 'Create and manage notebooks, notes, to-dos, tags, and attachments; run search, sync, and import/export'.

Add an explicit trigger clause such as 'Use when the user wants to automate Joplin notes, notebooks, to-dos, tags, sync, or import/export from the command line'.

Include natural trigger terms users would actually say — 'Joplin notes', 'notebooks', 'to-dos', 'sync' — to improve trigger term coverage beyond the app name.

DimensionReasoningScore

Specificity

"Command-line interface for Joplin workflows" names the domain and mechanism ("the real joplin terminal backend") but lists no concrete actions — no mention of notes, to-dos, tags, sync, or search — matching the anchor 'Names the domain but actions are minimal or generic'. It falls short of anchor 3 because no specific concrete action is enumerated.

2 / 5

Completeness

The 'what' is clear (a CLI for Joplin workflows backed by the real terminal binary), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not score 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords like "Joplin", "command-line interface", and "terminal" are present, but common natural terms a user would say — notes, notebooks, to-dos, tags, sync — are missing, matching 'Some relevant keywords but missing common variations or synonyms'. Not score 4 because keyword coverage is limited to the app name and CLI jargon.

3 / 5

Distinctiveness Conflict Risk

"Joplin" identifies a clear niche (a specific note-taking app's CLI), so wrong-skill triggering is unlikely, but the description lacks explicit distinct triggers and could overlap with any other Joplin-related skill, matching 'Mostly distinct; minor overlap risk'. Not score 5 because distinct triggers are not articulated.

4 / 5

Total

12

/

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

joplin/agent-harness/cli_anything/joplin/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.