create

Create Note

Write a Markdown note into the Obsidian vault Claude Code is running in. This skill owns vault conventions — callers supply content, not layout.

Input

$ARGUMENTS:

• --title (required) — note title, also the filename
• --content (required) — Markdown body
• --folder (optional) — subfolder within the vault; defaults to the vault root
• --frontmatter (optional) — JSON object of extra frontmatter fields

Step 1 — Locate the vault

Walk up from the current working directory looking for a .obsidian/ directory. The first ancestor containing one is the vault root.

d="$PWD"
while [ "$d" != "/" ]; do
  [ -d "$d/.obsidian" ] && { echo "$d"; break; }
  d="$(dirname "$d")"
done

If no .obsidian/ is found, stop and say so — do not guess a path and do not write outside a vault. Ask the user to run from inside their vault or to name the target vault explicitly.

There is no config file. The vault is wherever the session is.

Step 2 — Read the vault's conventions

If the vault root has a CLAUDE.md, read it first and follow any conventions it states — folder layout, frontmatter fields, tagging, wikilink rules, daily-note behaviour. A vault's own documented conventions override the defaults below.

Reading it is not optional and neither is acting on it. Delegation here has silently failed before: a clipping was written correctly and its daily-note link was never added, because "follow any conventions it states" was treated as advisory. Steps 3a and 3b make the two that are almost always stated explicit.

Step 3 — Build the note

Filename — from the title, with / \ : * ? " < > | replaced by -, and whitespace trimmed. If the file already exists, append 2, 3, … rather than overwriting.

Frontmatter — always include title and created (today, YYYY-MM-DD), then merge in anything from --frontmatter. Preserve the caller's values on conflict.

Folder — --folder if given, else the vault root. Create the folder if it does not exist.