What does this skill do, and when should you use it?
This is one standalone Agent Skill in the claude-obsidian repository, focused on Obsidian Flavored Markdown. It covers wikilinks, embeds, callouts, Properties, tags, highlights, math, code blocks, tables, Mermaid diagrams, and footnotes. It fits users who create or edit Obsidian knowledge pages and need reliable syntax, but it is not the repository’s full ingestion, retrieval, research, or vault-maintenance workflow. The README recommends kepano/obsidian-skills as the authoritative substrate and presents this Skill as a self-contained fallback.
Provides syntax guidance and examples for creating or editing Obsidian pages; explains wikilinks such as [[Note Name]], embeds such as ![[Note Name]], callouts such as [!note], YAML Properties, tags, ==highlights==, MathJax/KaTeX formulas, code blocks, tables, Mermaid diagrams, and footnotes; and documents common mistakes including using ordinary Markdown links for internal notes, putting HTML inside callouts, nesting frontmatter objects, or using ISO datetimes in Properties.
- An Obsidian user creating a knowledge page that needs wikilinks, aliases, heading anchors, or block links.
- A knowledge-management user filing material that includes images, PDFs, audio, or embedded notes.
- A researcher writing Obsidian pages with Properties, tags, equations, tables, or Mermaid diagrams.
- A vault maintainer repairing broken links, invisible callouts, or malformed frontmatter.
How do you install this skill?
- Write/Edit can directly change user notes; confirm target files and retain version control or backups before use.
- Verify callout types, Properties rules, and Mermaid support against the installed Obsidian version.
- The preferred substrate depends on GitHub marketplace access; network-restricted environments should preserve the local fallback.
- The skill has no dedicated tests, so CI results for other repository scripts should not be treated as validation of this syntax reference.
- Local filesystem
The repository README documents two main collection-level installation methods: clone it with git clone https://github.com/AgriciDaniel/claude-obsidian && cd claude-obsidian && bash bin/setup-vault.sh; or run claude plugin marketplace add AgriciDaniel/claude-obsidian, followed by claude plugin install claude-obsidian@agricidaniel-claude-obsidian. The target Skill is at skills/obsidian-markdown/SKILL.md. The README does not document the exact standalone installation directory for this Skill in other clients.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/AgriciDaniel/claude-obsidian.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/obsidian-markdown" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Use it when creating or editing an Obsidian page with triggers such as write obsidian note, obsidian syntax, wikilink, callout, embed, or obsidian markdown. Its declared tools are Read, Write, and Edit. Select the relevant syntax section and follow its rules for internal links, frontmatter, tags, and callouts.
What are this skill's strengths and limitations?
- Covers the main Obsidian Markdown extensions with reference examples.
- Calls out practical pitfalls for wikilinks, embeds, callouts, and Properties.
- Uses only generic name, description, and file-editing tool declarations, with no listed platform-specific dynamic commands or subagent mechanism.
- The repository is open source under the MIT license.
- It is a syntax-reference Skill, not an automatic source-ingestion, knowledge-graph, retrieval, or vault-maintenance system.
- The README does not provide standalone installation instructions for this individual Skill on non-Claude Code clients.
- It recommends the kepano/obsidian-skills version as the authoritative reference, so this fallback may need updates as Obsidian syntax evolves.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Obsidian Markdown Syntax Assistant this page | 45 · Not recommended | ★ 16k | 1mo ago | MIT |
| Obsidian Markdown Editor | 57 · Use with care | ★ 50k | 1mo ago | MIT |
| LLM Wiki Manager | 51 · Use with care | ★ 71 | 1mo ago | MIT |
| Conversation Archivist | 49 · Use with care | ★ 16k | 1mo ago | MIT |
| Obsidian CLI Knowledge Transport | 48 · Use with care | ★ 16k | 1mo ago | MIT |
The README compares this Skill with the same-named Skill in kepano/obsidian-skills, recommending the latter as the authoritative substrate and this version as a self-contained fallback.
How did FollowSkills review this skill?
The skill declares only Read, Write, and Edit, so its tool scope is relatively limited; however, Write/Edit can directly modify user notes, while confirmation, backup, rollback, and sensitive-data handling are unspecified. It also recommends an external marketplace dependency without sufficient data-flow disclosure, so points are deducted.
The document is internally organized and supplies examples for the main syntax areas. Repository CI and tests exist, but the supplied evidence primarily covers other scripts, not the key paths of this Markdown reference. Several callout and compatibility claims lack version validation or diagnosable failure guidance, so the static score is limited.
Triggers, audience, and scenarios are reasonably clear, covering wikilinks, embeds, callouts, properties, and related syntax. Non-fit boundaries, a precise input/output contract, and Chinese examples are missing. The preferred substrate depends on a GitHub marketplace path that may be hard to reach from mainland China, although the local fallback reduces that risk.
The skill has frontmatter, layered sections, tables, positive and negative examples, and some limitation guidance; the repository supplies an MIT license and general CI. The skill itself lacks versioning, changelog, maintenance ownership, and an update path, and its substrate-preference rule adds maintenance assumptions, so points are deducted.
As an Obsidian Markdown cheat sheet, the examples are directly usable and cover core authoring tasks. Static review did not verify rendering in the target Obsidian version; some rules may be oversimplified, and comparative evidence against official references or alternatives is limited, so points are deducted.
The file contains auditable code blocks, tables, and repository references, and the repository has CI. However, there are no dedicated tests for this skill, no third-party execution evidence, and no substantial cross-source corroboration; key correctness claims therefore remain primarily author assertions, so points are deducted.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →