obsidian-markdown
by MarsWang42obsidian-markdown helps agents create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, frontmatter, tags, checklists, and math. Best for vault notes, team wikis, and knowledge base writing where Obsidian-specific syntax must stay valid.
This skill scores 68/100, which means it is acceptable to list for directory users who want Obsidian-specific Markdown help, but they should treat it as a syntax reference more than a tightly operational workflow skill. The repository gives enough evidence that an agent can trigger it correctly from Obsidian, wikilink, callout, frontmatter, tag, embed, or note-editing requests, yet it provides limited execution scaffolding beyond documentation.
- Strong triggerability: the frontmatter clearly states when to use it for Obsidian .md files, wikilinks, callouts, frontmatter, tags, embeds, and notes.
- Substantial real content: the long SKILL.md covers Obsidian-flavored Markdown syntax with many headings and code examples rather than being a placeholder.
- Useful agent leverage for formatting tasks: it should reduce guesswork versus a generic prompt when producing Obsidian-specific syntax like wikilinks, embeds, and callouts.
- Operational support is thin: there are no scripts, references, rules, or install command, so agents mostly rely on prose examples instead of executable guidance.
- Some trust/fit ambiguity remains because placeholder markers are present and the evidence shows limited constraints or decision rules for edge cases.
Overview of obsidian-markdown skill
What the obsidian-markdown skill does
The obsidian-markdown skill helps an agent write and edit valid Obsidian Flavored Markdown instead of generic Markdown. It is designed for notes, knowledge base pages, and documentation that rely on Obsidian-specific syntax such as [[wikilinks]], ![[embeds]], callouts, tags, frontmatter properties, checklists, and math.
Who should use obsidian-markdown
This skill is best for people building or maintaining an Obsidian vault, team wiki, research notebook, or internal docs set where note structure matters as much as prose. If your real job is “turn rough notes into usable Obsidian pages” or “keep note syntax clean across a knowledge base,” obsidian-markdown is a better fit than a plain writing prompt.
Why it is different from a normal Markdown prompt
A normal prompt may produce readable Markdown but still miss Obsidian conventions, especially around wikilinks, embeds, callouts, and metadata. The obsidian-markdown skill narrows the model toward Obsidian-aware output, which reduces cleanup and makes it easier to generate notes that can be dropped into a vault with less manual fixing.
How to Use obsidian-markdown skill
Install context and what to read first
This skill lives at EN/.agents/skills/obsidian-markdown in MarsWang42/OrbitOS, and the key file is SKILL.md. There are no helper scripts, rules, or references in the provided tree, so most of the usable guidance comes from that single file. Read SKILL.md first if you want to confirm supported syntax and examples before using obsidian-markdown install steps in your own workflow system.
What input makes obsidian-markdown work well
obsidian-markdown usage is strongest when you provide:
- the note type: meeting note, concept page, daily note, MOC, reference note
- the required Obsidian features:
[[links]], callouts, YAML frontmatter, tags, embeds - your vault conventions: heading style, property names, filename format, tag rules
- source material: rough bullets, transcript, outline, or existing note to clean up
A weak request is “write this in Obsidian format.”
A strong request is: “Convert these raw research bullets into an Obsidian note with YAML frontmatter, [[wikilinks]] to related concepts, one > [!summary] callout, and action items as task checkboxes.”
How to turn a rough goal into a usable prompt
For obsidian-markdown for Knowledge Base Writing, ask for both structure and syntax. A practical prompt pattern is:
- goal: what the note is for
- audience: just you, a team, or public docs
- vault rules: naming, tags, aliases, status fields
- output constraints: one file, no explanatory text, valid Obsidian Markdown only
Example:
“Create an Obsidian concept note from these bullets. Use YAML frontmatter with tags, aliases, and status. Add [[related notes]], keep headings shallow, and include a > [!note] callout for definitions. Output only the final Markdown.”
Suggested workflow and practical tips
Use obsidian-markdown guide style prompts in two passes:
- Generate the note skeleton: frontmatter, headings, links, callouts.
- Refine content quality: tighten summaries, fix link targets, normalize tags.
This skill appears syntax-heavy rather than workflow-automated, so you should verify:
- frontmatter keys match your vault conventions
- wikilinks point to real note titles
- embeds use the exact target file name
- callout types match what your vault theme supports
If you are migrating existing Markdown, ask the model to preserve content while converting only syntax. That reduces accidental rewrites.
obsidian-markdown skill FAQ
Is obsidian-markdown worth using over a normal prompt?
Yes, if syntax fidelity matters. The biggest value of obsidian-markdown is not better prose by itself; it is reducing errors in Obsidian-specific formatting. If you only need plain Markdown for GitHub or a static site, this skill may be unnecessary.
Is this good for beginners using Obsidian?
Yes, especially if you know the kind of note you want but not the exact syntax. The examples in SKILL.md cover core formatting and Obsidian-specific constructs, so the skill can help beginners produce valid notes faster. You still need to know your own vault naming and metadata conventions.
What are the boundaries of the obsidian-markdown skill?
This skill is focused on creating and editing Obsidian Flavored Markdown. It is not a vault management tool, link validator, plugin configurator, or publishing pipeline. It helps generate correct note text, but it does not know whether your target notes, tags, or property schemas already exist unless you supply them.
How to Improve obsidian-markdown skill
Give obsidian-markdown stronger vault-specific instructions
The fastest quality gain comes from adding your real conventions. Tell the model:
- preferred frontmatter fields
- allowed tag hierarchy
- whether to use
[[wikilinks]]or Markdown links - callout types you actually use
- filename or title rules
Without this, obsidian-markdown may produce technically valid output that still feels wrong for your vault.
Prevent common output failures
The most common issues are invented links, inconsistent properties, over-structured notes, and generic summaries. To prevent them, provide a short “do and don’t” list such as:
- use only these existing note names
- do not create tags outside this set
- keep to three heading levels max
- preserve original wording for quoted research notes
Iterate after the first draft
The best obsidian-markdown usage is iterative. After draft one, ask for targeted fixes instead of full rewrites:
- “Normalize frontmatter keys to my schema.”
- “Replace placeholder wikilinks with plain text where targets are unknown.”
- “Turn this long section into one summary callout and three bullet groups.”
- “Keep content unchanged, only convert to Obsidian syntax.”
That keeps the note stable while improving format quality.
When not to use obsidian-markdown
Skip obsidian-markdown skill if your output is going to a non-Obsidian destination, or if you need repository-aware automation rather than formatting help. The current repository evidence points to a document-based syntax skill, not a richer toolchain with scripts or validation helpers. Use it when your bottleneck is note formatting quality, not system integration.