Agent skill · software engineering · hkuds
cli-anything-joplin
Command-line interface for Joplin workflows using the real joplin terminal backend
Why this skill is useful
Adds a command-line interface with executable scripts for automating Joplin workflows that are not available in public documentation.
What it needs
Requires python installed locally. About 2k tokens when loaded. Last updated 2026-08-03. 46,739 stars on the source repository.
What this skill does
cli-anything-joplin Use this skill to automate Joplin notebook, note, to-do, tag, attachment, search, sync, and import/export workflows through a stateful harness backed by the real joplin terminal binary. Requirements Python 3.10+ Joplin terminal binary available as joplin Optional: pass --profile to target a specific Joplin profile Install Usage JSON output contract When --json is enabled, commands return: ok: boolean command: stable command identifier such as notes.list, todos.toggle data: command payload error: null on success, or { type, message } on failure Command groups project: new, open, save, info, json, status notebooks: list, create, use, remove notes: list, create, set, get, remove, copy, move, rename todos: list, create, toggle, clear, done, undone tags: list, add, remove, notetags, tagnotes search: run sync: run (--target, --upgrade, --use-lock) interop: import, export config: get, set, list, export, import-file attach: add status: show, restore backend: version, dump, keymap, geoloc, export-sync-status server: status, start, stop e2ee: status, target-status, decrypt, decrypt-file session: status, undo, redo, history Agent guidance Prefer --json for parseable output. Use --project when running multi-step workflows so history is persisted. One-shot mutating commands auto-save the project unless --dry-run is set. REPL mode does not auto-save; run project save explicitly. Some Joplin CLI builds gate search behind GUI mode; if you see "only available in GUI mode", treat search as best-effort. Joplin 3.6.x can have a broken version command in npm global layouts; the harness falls back to installed package metadata for backend version, probing the symlink-resolved binary directory, the Windows-style sibling nodemodules/joplin, the Unix-style parent lib/nodemodules/joplin, and finally npm root -g. Backend stdout/stderr in command results are verbatim; do not assume warnings were stripped from note bodies or exports. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills hkuds/skills--f90430