agentleFS
Sign inStart free
AgriciDanielAgriciDaniel/claude-obsidian/skills/obsidian-markdown/SKILL.md

obsidian-markdown

Skill16k starsChanged 52 days agoMITView on GitHub

Explain, draft, or validate Obsidian Flavored Markdown syntax: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user explicitly requests Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.

We split this skill into the rules it gives an agent

10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 76 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this as a compact fallback for Obsidian-specific syntax.

    line 8
  2. Very specific:

    Every ../wiki/references/ link in this file resolves the same way, relative to this skill's own directory under $PRODUCT_ROOT, never …

    line 22
  3. Distinctive:

    Never write a note directly.

    line 41
  4. Very specific:

    Use flat YAML properties and YYYY-MM-DD dates.

    line 45
  5. Very specific:

    Do not nest objects in generated wiki properties.

    line 66
  6. Very specific:

    Use year/2026 or y2026, or store a number in a year property.

    line 68
  7. Distinctive:

    Verify every internal target, heading, and block reference that can be checked locally.

    line 138
  8. Distinctive:

    Keep evidence wording distinct from inference and preserve source locators.

    line 140
  9. Distinctive:

    Ensure code fences and callout quoting are balanced.

    line 141
  10. Distinctive:

    Run deterministic wiki lint after a requested mutation and report remaining findings without silently repairing them.

    line 142

“Common” is measured: kept by at least 6 in 10 of the 76 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Obsidian Flavored Markdown

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.

Properties

Use flat YAML properties and YYYY-MM-DD dates. Quote wikilinks inside YAML.

---
type: concept
title: "Contextual Retrieval"
created: 2026-07-11
updated: 2026-07-11
status: developing
tags:
  - retrieval
  - ai/knowledge
aliases:
  - Context-aware retrieval
related:
  - "[[Retrieval]]"
sources:
  - "[[Anthropic Contextual Retrieval]]"
---

Do not nest objects in generated wiki properties. Use block lists rather than inline YAML arrays. A numeric-only tag is invalid in Obsidian even when quoted as a YAML string. Use year/2026 or y2026, or store a number in a year property. Tags need at least one non-numeric character; valid Unicode tags remain supported. See Tags, checked 2026-10-17. Keep unknown existing properties unless the requested edit changes them.

Wikilinks and embeds

[[Note Name]]
[[Note Name|Display text]]
[[Note Name#Heading]]
[[Note Name#^block-id]]
[[Folder/Note Name]]

This paragraph is addressable. ^evidence-block

![[Note Name#Summary]]
![[diagram.png|480]]
![[paper.pdf#page=3]]

Match the target filename exactly. Use a vault-relative folder path when a basename is ambiguous. Use standard Markdown links for external URLs; use wikilinks for this vault's notes.

Callouts

> [!note]
> Supporting context.

> [!warning] Review required
> This claim has contradictory evidence.

> [!question]- Open question
> What evidence would resolve this?

- starts collapsed and + starts expanded. Common built-in types include note, abstract, info, todo, tip, success, question, warning, failure, danger, bug, example, and quote. Preserve custom vault callout types rather than rewriting them.

Other Obsidian syntax

#inline-tag #nested/tag

==Highlighted text==

Visible text %%hidden comment%%

Inline math: $E = mc^2$

$$
\int_0^1 x^2\,dx = \frac{1}{3}
$$

```mermaid
flowchart LR
  Source --> Claim
```

Standard CommonMark/GFM headings, lists, tasks, tables, code fences, and footnotes remain valid. Avoid HTML when native Markdown is sufficient.

Validate a drafted note

  • Parse the YAML boundary and keep property types consistent.
  • Verify every internal target, heading, and block reference that can be checked locally; never fabricate a target to make a link look complete.
  • Keep evidence wording distinct from inference and preserve source locators.
  • Ensure code fences and callout quoting are balanced.
  • Run deterministic wiki lint after a requested mutation and report remaining findings without silently repairing them.

For source-cited pages, also follow provenance.md. Report the transaction operation ID and exact changed paths after an applied edit.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about AgriciDaniel/claude-obsidian

The biggest 5 of 68 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 68

Talked about on GitHub, YouTube and Bluesky (68 times).

On GitHub · 37

32 more on GitHub

On YouTube · 25

20 more on YouTube

On Bluesky · 6

1 more on Bluesky
  • Other versions81 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 81

    1. kepano/obsidian-skills★ 49ksame name
    2. anbeime/skill★ 7.9ksame name
    3. breferrari/obsidian-mind★ 5.4ksame name
    4. Atmosphere/atmosphere★ 3.8ksame name
    5. heyitsnoah/claudesidian★ 2.6ksame name
    6. pedronauck/skills★ 641same name
    7. freestylefly/canghe-skills★ 461same name
    8. benoror/obsidianos_work★ 166same name
    9. kv0906/pm-kit★ 138same name
    10. songzhuozhu/obsidian-llm-wiki★ 121same name

    71 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use knap, obsidian-cli and 4 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • lucasmaher-hashSkill

      knap

      Render Markdown from templates and structured data using Knap CLI. Use when the user asks to apply a Knap template, turn JSON or CSV data into notes, batch-generate Markdown files, or format Defuddle output into a note.

      Also in 4 projects that use this

    • jykimSkill

      obsidian-cli

      Interact with Obsidian using the official CLI to read, search, create, and manage notes, daily notes, tasks, properties, and more. Use when the user wants to query or manipulate vault content via the obsidian command.

      Also in 37 projects that use this

    • BCS1037Skill

      mermaid-visualizer

      Transform text content into professional Mermaid diagrams for presentations and documentation. Use when users ask to visualize concepts, create flowcharts, or make diagrams from text. Supports process flows, system architectures, comparisons, mindmaps, and more with built-in syntax error prevention.

      Also in 3 projects that use this

    • 0xHoneyJarSkill

      qmd

      Local markdown search engine for knowledge bases, notes, and documentation. Combines BM25 full-text search, vector semantic search, and LLM re-ranking. Use when searching through markdown notes, retrieving documents, or managing knowledge collections.

      Also in 4 projects that use this

    • VercelSkill

      find-skills

      Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

      Also in 13 projects that use this

    • AnthropicSkill

      docx

      Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

      Also in 10 projects that use this

  • In this repository17 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free