create
/create
Write a note into the current Obsidian vault. Use when content is already in hand and needs saving as a note — including when another skill (such as notes:clip) has fetched content and needs it filed. Handles frontmatter, folder placement, filename sanitising, and collision avoidance.
- Author
- mayank-io ↗
- Repository
- mstack ↗
- Licence
- MIT
- Last repository change
- 12.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 12.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Write a note into the current Obsidian vault. Use when content is already in hand and needs saving as a note — including when another skill (such as notes:clip) has fetched content and needs it filed. Handles frontmatter, folder placement, filename sanitising, and collision avoidance.
Original author description
Write a note into the current Obsidian vault. Use when content is already in hand and needs saving as a note — including when another skill (such as notes:clip) has fetched content and needs it filed. Handles frontmatter, folder placement, filename sanitising, and collision avoidance.
How it works
- Input
- Step 1 — Locate the vault
- Step 2 — Read the vault's conventions
- Step 3 — Build the note
- Step 4 — Write the file
- Step 4.5 — Make the attachments local. Always.
- Step 5 — Link it into today's daily note
- Step 6 — Verify, then report
- Errors
SKILL.md preview
---
name: create
description: "Write a note into the current Obsidian vault. Use when content is already in hand and needs saving as a note — including when another skill (such as notes:clip) has fetched content and needs it filed. Handles frontmatter, folder placement, filename sanitising, and collision avoidance."
---
# 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.
```bash
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.
**Links in the body** — if the vault documents an entity-linking rule (stock tickers as `[[$AAPL]]`, people as `[[@Name]]`, dates as `[[YYYY-MM-DD]]`), apply it to the content you were handed. The caller supplies text; converting bare mentions into the vault's link syntax is this skill's job, because this skill is the one that read the conventions.
### Entity linking — scan, resolve, then create
**Run these in order. Each step exists because skipping it has produced a wrong note.**
**1. Scan for company and organisation NAMES, not for ticker-shaped strings.** Every company named in the body is a candidate for a page and a link. A note about "SpaceX" that links `[[$NVDA]]` because *that* one was already written as a symbol, while leaving the actual subject unlinked, is the failure this step prevents. Read the content for entities; do not pattern-match for `$`.
**2. Resolve the official symbol before writing any link. A ticker is a fact to look up, never a string to construct.**
```bash
# Authoritative for US listings. A descriptive User-Agent is REQUIRED — SEC returns 403 without one.
curl -sL --max-time 30 -A '<you>@<domain> research' https://www.sec.gov/files/company_tickers.json \
| python3 -c "import sys,json;[print(str(v['cik_str']).zfill(10),v['ticker'],v['title']) for v in json.load(sys.stdin).values() if '<COMPANY>' in v['title'].upper()]"
# Cross-check the symbol actually trades.
curl -s -A 'Mozilla/5.0' "https://query1.finance.yahoo.com/v8/finance/chart/<SYM>?range=1d&interval=1d"
# -> meta.instrumentType == "EQUITY", meta.longName, meta.fullExchangeName
```
**The symbol is frequently not an abbreviation of the name.** Space Exploration Technologies Corp. trades as **`SPCX`**, not `SPACEX`. Guessing produced a duplicate page, a wrong "private company" framing, and a note asserting that figures were unverifiable when a 10-Q had already been filed.
**3. Search existing pages by `name:` and `aliases:`, NEVER by filename.**
```bash
grep -ril "<company name>" Notes/Tickers/ # matches frontmatter name/aliases
# NOT: ls Notes/Tickers/ | grep '^\$SPACEX\.md' # returns nothing, looks like "no page exists"
```
A filename search answers "is there a page named after my guess", which is a different question from "does this company have a page". The page for SpaceX is `$SPCX.md`, and its frontmatter carries `name: SpaceX` plus `aliases: ["SpaceX", "Space Exploration Technologies"]` — precisely so a name search finds it.
**4. Create a page only after both 2 and 3 come back empty**, from the vault's ticker template. Carry the resolved symbol, and set `aliases:` to every name the company is called in the wild, so the next scan finds it by step 3.
**5. Never invent a symbol as a placeholder.** If a public company's symbol cannot be resolved, say so and leave the mention unlinked rather than minting one — an invented symbol becomes a duplicate page that later has to be found and merged. If no symbol exists because the company is private, follow the vault's private-company convention; if the vault documents none, ask rather than inventing.
**6. Link every resolved entity**, including in frontmatter where the vault uses a `tickers:` field.
### Wikilink and filename hygiene
**1. 🔴 Never put a path inside a wikilink.** Obsidian resolves `[[Name]]` by **basename across the whole vault**; a folder prefix makes it unresolvable and it fails *silently*, rendering as plain text rather than erroring.
```
✅ [[Some Clipping Title]] 🔴 [[Clippings/Some Clipping Title]]
```
Attachment embeds are the exception — `![[attachments/foo.jpg]]` is correct, because that path is relative to the note.
**Corollary:** moving a note never breaks its inbound wikilinks, so the prefix buys nothing even as insurance.
**2. 🔴 No parentheses in filenames.** Commas, dashes and `$`/`@` prefixes are fine; `(` and `)` are not. A vault with `"useMarkdownLinks": true` and `"alwaysUpdateLinks": true` rewrites links as `[text](path)` on any move or rename, and **an unescaped `)` in the path terminates the link early**. Such a filename works until something moves, then breaks invisibly. Strip parentheses when sanitising the title — fold the parenthetical into the `title:` frontmatter instead, where it is harmless.
**3. ⚠️ Verify links vault-wide, not only in the files just written.** A note you never touched can hold a link to a note you just created or renamed, and the reverse — your new note's links are only half the check.
## Step 4 — Write the file
## Step 4.5 — Make the attachments local. Always.
**Run this on every note you write, immediately after writing it. It is not optional and it is not only for clippings.**
```bash
python3 "${CLAUDE_PLUGIN_ROOT}/skills/clip/scripts/attachments.py" "<absolute path to the note>" --obsidian
```
Run it **outside the command sandbox**: `--obsidian` talks to the running Obsidian app, and the sandbox blocks that.
What it does, in one pass:
| In the note | Becomes |
|---|---|
| ``, a remote image | downloaded into `<note folder>/attachments/` and re-embedded by relative path |
| `` or `<img src="data:…">` | decoded into a file and re-embedded |
| an inline `<svg>…</svg>` | saved as a valid `.svg` file and re-embedded |
| a remote embed that is not an image (a YouTube player) | left alone, listed under `skipped` |
Then it verifies **every** embed in the note, whoever wrote it: the file exists, is not empty, is not an iCloud placeholder, and (for SVG) parses. With `--obsidian` it also asks the app to resolve each embed, which is the only check that sees the note as the reader will.
**Read the result.** stdout is one JSON object; the exit code is the verdict.
- **Exit 0** — every embed is local and present. Report the count (`local_ok`) and move on.
- **Exit 1** — something is missing, empty, a placeholder, or failed to download. `problems` and `failed` name each one. **Fix it or report the note as incomplete; never report the note as done.**
- `obsidian.status: "skipped"` — the app or its CLI was not reachable. The file checks still ran; say that the Obsidian check was skipped and why. A skip is not a pass.
Files are named `<note-name-slug>-NN.<ext>` by default; pass `--prefix` to match the source's naming (`karpathy-2105819303471976479`). Fenced code blocks are never rewritten. A second run changes nothing.
**Why a script and not a checklist item:** "every embedded image path should exist" was a sentence in this skill for months, and notes still shipped with base64 images inlined at 1.4 MB, raw `<svg>` markup, and seven SVG files that no XML parser would open. A check that depends on being remembered is not a check.
## Step 5 — Link it into today's daily note
Most vaults want every new note discoverable from the day it was made. Unless the vault's `CLAUDE.md` says otherwise:
1. Find today's daily note — commonly `Daily Notes/YYYY-MM-DD.md`. Match the vault's actual folder and date format; do not assume.
2. Append a link to the new note: `- [[Note Title]]`.
3. If the daily note does not exist, create it from the vault's daily-note template if there is one.
## Step 6 — Verify, then report
**Check before claiming.** Every `[[wikilink]]` written should resolve to a real file, or be a deliberate stub the vault's conventions call for. Escaped pipes in tables (`[[Target\|Alias]]`) produce false "broken" hits — strip the trailing backslash before comparing. **Attachments are verified by Step 4.5's script, not by eye**: state its result ("9 of 9 attachments local, Obsidian resolves all 9"), or what it flagged.
**Say what happened to the daily note either way** — "linked into `Daily Notes/2026-08-24.md`", or that you did not and why. Never leave the caller to assume it happened.
Then print the path as the **final line** in machine-parseable form so callers can chain on it:
```
OUTPUT_FILE:/absolute/path/to/vault/Folder/Note Title.md
```
Print a human-readable confirmation before that line if useful, but the `OUTPUT_FILE:` line must be last.
## Errors
- **No vault found** — stop, explain, do not write.
- **Missing `--title` or `--content`** — stop and say which.
- **Folder missing** — create it.
- **File exists** — never overwrite; suffix the name.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · mayank-io/mstack | 100 | MIT |
| verygoodopensource/vgv-wingspan | 100 | MIT |
| crisandrews/clawcode | 100 | MIT |
| digital-stoic-org/agent-skills | 100 | MIT |
| turalowski/agents | 100 | MIT |
| turalowski/agents | 100 | MIT |
| turalowski/agents | 100 | MIT |
| Borda/AI-Rig | 100 | Apache-2.0 |
| ninjanazal/team-chat | 100 | MIT |
Database snapshot: 13.11.2026 · package version f0cce7a93593 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90to-note
Save content as a Markdown note in the user's Obsidian vault. Use for /to-note, or when asked to save, record, or send something to Obsidian or the notes vault. - 100save-local-file
File a local file — PDF, image, or document already on disk — into the current Obsidian vault as a clipping with the file attached. Use when the user gives a file path and wants it saved to their vault, or when notes:clip has fetched a file and needs it filed. For URLs, use notes:clip instead. - 100obsidian-vault
Vault structure, file naming, frontmatter, tags, tasks, and linking conventions. Use when: "vault structure", "file naming", "frontmatter", "wiki links", "obsidian", "tags", "tasks", "create note", "organize notes". - 90note
Use when working with files in ~/Notes (the user's Obsidian vault). Covers vault structure (PARA), file naming, frontmatter, icons, templates, kanban boards, and the obsidian CLI. - 100make-note
Create well-structured notes in Obsidian with intelligent tag suggestions. Use this skill whenever the user asks to create a note, make a note, save something to Obsidian, capture a thought, or write something to their vault. Also trigger when the user says "note this", "add to… - 95obsidian-markdown
Obsidian Flavored Markdown syntax reference - wikilinks, embeds, callouts, properties/frontmatter, tags, comments, block IDs. Use when creating or editing .md files in an Obsidian vault, when linking or embedding notes, when writing callouts or note frontmatter, or when the user…