obsidian-markdown

1# Obsidian Flavored Markdown
2 
3Use this as a compact fallback for Obsidian-specific syntax. Prefer a separately
4installed `kepano/obsidian-skills` `obsidian-markdown` skill when available,
5then current [Obsidian Help](https://help.obsidian.md/), for detailed or
6version-sensitive questions.
7 
8Resolve the installed product root from this skill's own location, not from the
9vault or current working directory:
10 
11```bash
12PRODUCT_ROOT=/absolute/path/to/installed/claude-obsidian
13CORE="$PRODUCT_ROOT/scripts/claude-obsidian.py"
14test -f "$CORE"
15```
16 
17Every `../wiki/references/` link in this file resolves the same way, relative
18to this skill's own directory under `$PRODUCT_ROOT`, never relative to the
19selected vault's `wiki/` directory.
20 
21Answer syntax questions read-only. If the user requests a vault edit, draft the
22complete note, read [operation-transactions.md](../wiki/references/operation-transactions.md),
23and build one `claude-obsidian.transaction.v1` bundle with
24`operation_type: markdown` and only `wiki/` targets. Inspect it, then set
25`APPROVAL_SHA256` to the returned `approval_sha256` after review and apply it
26through the same vault-bound plan. A canonical page create or removal includes
27an active index or MOC update in that bundle; update the overview only when its
28stable high-level synthesis changed:
29 
30```bash
31python3 "$CORE" transaction inspect "$BUNDLE" --vault "$VAULT"
32python3 "$CORE" transaction apply "$BUNDLE" --vault "$VAULT" \
33  --approved-plan-sha256 "$APPROVAL_SHA256"
34```
35…