Obsidian Markdown

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — USE REQUIREMENTS DISCLOSED FIRST: this skill works on your own Obsidian vault and runs through the portable core of the claude-obsidian repository, scripts/claude-obsidian.py, which lives at the repository root OUTSIDE this skill's folder, together with the shared contracts it links to (under skills/wiki/references/ in that same product root, for example the provenance and operation-transaction contracts). Installing this listing copies only this skill's folder: without a full claude-obsidian installation (the core, its contracts, python3 to run it, and a selected user vault) the skill cannot run its transactions as designed. The family orchestrator is the separate wiki skill of the same repository. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Obsidian Markdown" for me. It explains, drafts and validates Obsidian Flavored Markdown syntax: flat YAML properties, wikilinks and embeds, callouts, tags, comments, highlights, block references, math and Mermaid, plus the Obsidian-specific rules that differ from plain Markdown (quote wikilinks inside YAML, no nested objects in generated wiki properties, a numeric-only tag is invalid, dates as YYYY-MM-DD). Use it only when you explicitly request Obsidian note formatting or syntax help, not for general Markdown or broad vault operations. Syntax questions are answered read-only. If you request a vault EDIT, it drafts the complete note first, then builds one claude-obsidian.transaction.v1 bundle of operation type markdown with only wiki/ targets in your vault, inspects it, and applies it only with the approval hash (APPROVAL_SHA256 pattern) through the portable core: it never writes a note directly. A canonical page creation or removal in that bundle carries its active index or MOC update with it. Before an edit it validates locally: YAML boundary and property types, every internal target, heading and block reference that can be checked (never fabricating a target to make a link look complete), balanced code fences and callout quoting, and it keeps evidence wording distinct from inference. For detailed or version-sensitive questions it prefers a separately installed kepano/obsidian-skills obsidian-markdown skill, then current Obsidian Help. After an applied edit it reports the operation ID and exact changed paths and runs a deterministic wiki lint, reporting remaining findings without silently repairing them. Repository: https://github.com/AgriciDaniel/claude-obsidian (the skill is the whole skills/obsidian-markdown/ folder at the pinned commit: SKILL.md only, 1 file) Pinned version: install the code at commit 2e545563172f97f02ecaaaab376ceea1246a0583 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/AgriciDaniel/claude-obsidian into a temporary folder, check out commit 2e545563172f97f02ecaaaab376ceea1246a0583, and copy the skills/obsidian-markdown/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 c7c04184ba81b1f8482e647a56899bfc9796daa20acbd68e78c57b406d4351bf If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md, a compact fallback reference for Obsidian-specific syntax. The core it runs (scripts/claude-obsidian.py) and the transaction and provenance contracts it links to live outside this folder, in the full claude-obsidian product root. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no note is drafted, validated or edited. - At use time, syntax questions are read-only. A requested vault edit is made only as one inspected transaction of operation type markdown, targets under wiki/ only, applied with the approval hash (APPROVAL_SHA256 pattern); a note is never written directly. - It validates before any edit (YAML, internal targets, headings, block references, fences and callout quoting) and never fabricates a link target; after an applied edit it runs deterministic wiki lint and reports remaining findings instead of silently repairing them. - Do not draft or edit any note, do not run any transaction or lint, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole obsidian-markdown folder into the agent's skills directory, in a folder named exactly "obsidian-markdown", keeping its single file (SKILL.md) at its root. 4. Verify with no network calls: frontmatter valid (name: obsidian-markdown), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that a full claude-obsidian installation (portable core and contracts at the product root) and my own Obsidian vault are required for its edit path, that syntax questions alone are read-only, and that note edits go only through reviewed transactions with wiki/ targets). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.