obsidian-markdown
skillCreate and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian syntax.
Agent Skills for Obsidian workflows and open formats, including Obsidian Markdown, Bases, JSON Canvas, the Obsidian CLI, and Defuddle web-page cleanup.
Agent Skills for Obsidian workflows and open formats, including Obsidian Markdown, Bases, JSON Canvas, the Obsidian CLI, and Defuddle web-page cleanup.
# In your agent, ask:
Create a test note using Obsidian-flavored Markdown with one wikilink and one callout.Each card below corresponds to a component identified in the repository research. Open a component record for its path, purpose, capabilities, dependencies, risks, and relationships.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian syntax.
Create and edit Obsidian Bases files with views, filters, formulas, properties, and summaries.
Create and edit JSON Canvas files containing nodes, edges, groups, and spatial relationships.
Operate an Obsidian vault through the Obsidian CLI, including supported plugin and theme-development tasks.
Extract clean, readable Markdown from a web page with Defuddle while removing navigation and other clutter that wastes context.
These capabilities are derived from the current first-party README and supporting documentation. Names follow upstream terminology so you can search the source documentation precisely.
Upstream treats this as a distinct part of kepano/obsidian-skills. In plain language, use this area when your task concerns npx skills. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of kepano/obsidian-skills. In plain language, use this area when your task concerns manually. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of kepano/obsidian-skills. In plain language, use this area when your task concerns skills. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Start with one capability card instead of asking the repository to do everything at once. This makes permissions, inputs, and output easier to understand.
Use a sample URL, copied repository, test document, or sandbox account. Keep production credentials and irreplaceable files out of the first run.
Watch Terminal output or the host application's activity view. If the behavior differs from the README, stop with Control + C or cancel inside the host before retrying.
Check generated files, diffs, API responses, logs, or previews. Never assume “command finished” means the result is correct.
Record the working command and non-secret configuration in your project's README. Store secrets in the documented environment file or password manager.
These examples are selected from the repository's first-party documentation. Replace obvious placeholders, keep quotation marks intact, and run them only in the context indicated by the surrounding explanation.
open "https://github.com/kepano/obsidian-skills#readme"Agent host skill configuration
A configuration file changes behavior without changing source code. Make one change at a time and keep a backup before editing JSON, TOML, YAML, or environment files.
skills/
Paths identify where the relevant implementation or generated files live. Paths beginning with ~ are inside your home folder.
None for the skills; target sites may require their own access
Prefer temporary, least-privileged credentials. Never commit .env, tokens, cookies, private keys, or session exports.
Optional web pages fetched by Defuddle
Check pricing, data retention, rate limits, and account permissions before enabling optional integrations.
git diff before committing.127.0.0.1 unless you intentionally secure and expose them.The manual reflects first-party files checked on August 18, 2026. It explains the indexed repository rather than promising that every optional third-party integration is available or safe.