Guide · Obsidian

Agent skills for Obsidian: files on disk, or the app's CLI

By SkillPicker Editorial · Published October 2, 2026 · 5 min read

An Obsidian vault is a folder of files, plus an app that understands those files. Skills split along that line. One family writes the files: Obsidian Flavored Markdown, Bases, and JSON Canvas. The other family talks to the running app through Obsidian's own command line. A third family treats the vault as a wiki, with raw sources kept apart from the notes distilled from them. Installing the wrong family is the usual failure. The CLI skill sits idle because the app was never enabled. The Markdown skill cannot search the vault the way the app can. The wiki skill refiles notes you only wanted appended.

Candidates below are from the Obsidian topic. The list is ranked by observed search demand. It is not a plugin directory.

Quick scan: three families

File skills: write the formats Obsidian actually uses

Plain Markdown is not quite Obsidian Markdown. Wikilinks, embeds, callouts, and properties are Obsidian Flavored Markdown. obsidian-markdown, from the kepano/obsidian-skills package, is the skill that targets that syntax. Use it when the task is a note. A generic writing skill will emit links and callouts the app does not recognize.

Bases are a different file. obsidian-bases creates and edits .base files: views, filters, formulas, and summaries over your notes. The syntax is documented in Obsidian's Bases help. A skill that "makes a table in Markdown" did not make a Base. If you want a database-like view that stays tied to note properties, ask for a .base file by name.

Canvas is a third file. JSON Canvas is an open format, originally created for Obsidian, stored as .canvas. json-canvas edits nodes, edges, and groups. obsidian-canvas-creator is a separate skill aimed at turning text into a mind map or a freeform canvas. Use the format skill when you care that the file stays valid. Use the creator when you care about the picture and will check the result in the app.

CLI skills: the app has to be in the loop

Obsidian's desktop CLI is documented at obsidian.md/help/cli. You turn it on in Settings, then General. Commands such as obsidian search and obsidian daily run against the open vault. The help page is explicit that the app must be running, and that the first command starts it. obsidian-cli in the kepano package, and the obsidian skill from openclaw, both wrap that interface. They can also reload plugins, run JavaScript, capture errors, and take screenshots. That is plugin and theme development, not note taking. Read that part of the SKILL.md before you allow it. A skill that can execute JavaScript inside your vault app has a wider blast radius than a skill that writes a Markdown file.

Do not confuse this with Obsidian Headless. Headless is the ob command for publishing a site without the desktop app, and it needs an Obsidian Publish subscription. A skill that says "CLI" and then talks about daily notes, tasks, and backlinks means the desktop CLI. A skill that says publish, dry-run, and site slug means Headless. They are not interchangeable, and a vault that is not a Publish site will not answer ob.

obsidian-organizer is a CLI skill with a narrower job: file new notes using a single folder-map note as the source of truth, and audit the folders you already have. It is the right shape when the vault's problem is "where does this go," and the wrong shape when you have not decided the map. Let it read the map before you let it move anything.

Wiki skills are a vault design, not a formatter

The obsidian-wiki set (llm-wiki, wiki-ingest, wiki-capture, wiki-lint, and the setup and status skills) describes a three-layer vault: raw sources, wiki pages distilled from them, and a schema for how pages are filed. Ingest copies a document or a URL in and writes interconnected pages. Lint looks for orphans, broken wikilinks, and stale pages. That is a knowledge-base practice. It is heavier than a student who wants one good note per lecture. For study notes specifically, obsidian-notes-creator is the smaller skill, and the students guide covers when a note skill helps and when it substitutes for studying.

vault-skill-factory goes one step further: it turns a cluster of wiki pages into a new Agent Skill. That is a publishing step. Skip it until the pages have been read and corrected. A generated skill preserves the mistakes in the wiki.

How to judge a candidate

• File or app: .md, .base, .canvas, or the live CLI. The SKILL.md should say which.
• Launch rule: if it calls obsidian, the desktop app and the CLI setting are part of the setup. If it calls ob, you are in Publish.
• Moves versus writes: creating a note is reversible. Reorganizing a vault is a migration. Require a folder map, and keep the vault in git or a copy.
• Wiki assumptions: a three-layer vault skill will mis-file notes in a vault that is a flat folder of daily notes.
• Plugin surface: reload, JavaScript, and DOM inspection are developer tools. Leave them out of a writing setup.

Where to start

The kepano package also includes skills for pulling readable Markdown out of web pages and for rendering templates. They are not required to edit a vault. Start with the one file type you actually open every day. The rest of the list is on the Obsidian topic.

Before you install

Pick with confidence.These guides explain how to compare skills and choose the one that fits. Read each skill's own SKILL.md before installing it. How this works