Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agricidaniel/obsidian-markdown
Explain, draft, or validate Obsidian Flavored Markdown syntax: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid.
Passed 17 of 22 test cases with the skill, and 14 of 22 without it.
and 3 more in the full report
5 fixed14 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Create YAML frontmatter for an Obsidian note 'RAG System'. Add a 'related' property pointing to '[[Retrieval Augmented Generation]]' and a 'sources' property pointing to '[[Paper 2024]]'. Write them unquoted as 'related: [[Retrieval Augmented Generation]]' like standard markdown links.
| Checked | Without skill | With skill |
|---|---|---|
| Quotes wikilink values in YAML frontmatter properties | Missed | Passed |
The instructions your model reads when the skill loads.
Use this as a compact fallback for Obsidian-specific syntax. Prefer a separately
installed kepano/obsidian-skills obsidian-markdown skill when available,
then current Obsidian Help, for detailed or
version-sensitive questions.
Resolve the installed product root from this skill's own location, not from the vault or current working directory:
PRODUCT_ROOT=/absolute/path/to/installed/claude-obsidian
CORE="$PRODUCT_ROOT/scripts/claude-obsidian.py"
test -f "$CORE"
Every ../wiki/references/ link in this file resolves the same way, relative
to this skill's own directory under $PRODUCT_ROOT, never relative to the
selected vault's wiki/ directory.
Answer syntax questions read-only. If the user requests a vault edit, draft the
complete note, read operation-transactions.md,
and build one claude-obsidian.transaction.v1 bundle with
operation_type: markdown and only wiki/ targets. Inspect it, then set
APPROVAL_SHA256 to the returned approval_sha256 after review and apply it
through the same vault-bound plan. A canonical page create or removal includes
an active index or MOC update in that bundle; update the overview only when its
stable high-level synthesis changed:
python3 "$CORE" transaction inspect "$BUNDLE" --vault "$VAULT"
python3 "$CORE" transaction apply "$BUNDLE" --vault "$VAULT" \
--approved-plan-sha256 "$APPROVAL_SHA256"
Never write a note directly.
Use flat YAML properties and YYYY-MM-DD dates. Quote wikilinks inside YAML.
test cases passed, vs 14 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.