When to choose it
Writing and editing Markdown inside an Obsidian vault with its additional syntax.
Choose it if: your task involves Obsidian-specific note syntax.
Look elsewhere if: you need note synchronization or a general browser integration.
What the source describes
- Guidance for internal note links, attachment embeds and callout blocks.
- Explains note properties and Obsidian-specific Markdown conventions.
Requirements
- Claude Code with Skill support.
- Node.js 22.20.0+ for the reviewed skills CLI 1.7.0, npm and download access.
- An Obsidian vault or sample notes you allow the agent to edit.
A focused Skill from Steph Ango’s Obsidian collection. The alternative obsidian plugin includes other Skills.
Install the focused Skill
- Choose the intended project. Run the focused install below from this project. The reviewed skills CLI 1.7.0 requires Node.js 22.20.0+ and npm. Read the upstream files and review the CLI’s installation scope and symlink or copy prompt.
- Check discovery. Confirm the Skill is listed for Claude Code in the same project.Shell • setup check
npx skills list --agent claude-code - Optional plugin distribution. This alternative installs the full Obsidian collection, including other Skills. Choose one distribution rather than installing duplicates.Shell • alternative plugin install
claude plugin marketplace add kepano/obsidian-skills claude plugin install obsidian@obsidian-skills --scope local
Run this command from the intended project folder after reviewing the source. The skills CLI targets Claude Code and defaults to project scope. Review its scope and symlink or copy prompt; use --global only if you want a user-wide installation.
npx skills add kepano/obsidian-skills --skill obsidian-markdown --agent claude-codeHow to use it
Ask naturally for Obsidian Markdown. Specify the allowed files and the syntax you need; a slash command is not required.
An original example for a bounded task. This request example is written by ClaudeStack; it is not a transcript of a tested session.
Create a project note with a status property, links to the existing Design and Meeting Notes pages, and a warning callout for unresolved decisions. Show me the proposed note before editing the vault.The external skills CLI collects installation telemetry and makes public-repository security-audit requests. Its README documents DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1 to disable both. ClaudeStack did not run this installer.
What to expect
The reviewed source describes these observations. ClaudeStack has not loaded or run this extension.
- A Markdown note with the requested Obsidian syntax.
- The result remains a file you can inspect in Obsidian’s reading view.
Self-check: Open the note in Obsidian and check its properties, link targets, attachments and callout rendering.
Troubleshooting
Links or embeds do not resolve
Check the exact vault filenames and attachment paths. Distinguish internal wikilinks from external Markdown links; this is an editorial check derived from the format guidance.
The Skill is not discovered
For the focused route, check skills list in the same project and confirm scope. For the plugin route, check /plugin and follow its activation instruction.
Disable or remove it
- For a project installation, run npx skills remove obsidian-markdown --agent claude-code from the same project. Add --global only when removing a global installation.
- Review any edits and generated artifacts separately; removing the Skill does not revert its work.
- If you installed the full plugin, disable or uninstall obsidian in /plugin at its installation scope.
Limitations & considerations
- Does not install Obsidian, configure synchronization or provide the Obsidian CLI.
- Vault edits need review before synchronization; target files and attachments must exist.
Source & review record
Our description is based on public documentation and manifests available on 2026-10-05. Installation formats were checked against Claude Code and the relevant installer documentation. No extension code was executed: this is a source review, not a runtime compatibility test or security audit.
- Original source and documentation
- Reviewed definition source
- License of the reviewed source
- Official plugin installation documentation
Repository last pushed at the time of review: 2026-09-15T14:43:57Z. This date does not prove that the extension works with a particular Claude Code release.
Usage guide sources
Upstream revision checked for this guide: 3ccff5338ea700537839b21900aa5358a0402c98. Command names and behavior in this guide are documentation and registration-source findings, not runtime verification.