Obsidian Note Create
Creates well-structured Obsidian notes with proper frontmatter, wikilinks, and template adherence. Detects available CLI (official, Yakitrak, or direct file write) and uses the best option. Reads vault conventions from CLAUDE.md before creating. Activates on "create note", "new note", "add to obsidian", or when creating markdown files in an Obsidian vault.
Install
npx skills add ElliotJLT/Claude-Skill-Potions --skill obsidian-note-creategit clone --depth 1 https://github.com/ElliotJLT/Claude-Skill-Potions.git /tmp/Claude-Skill-Potions
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skill-Potions/skills/obsidian-note-create ~/.claude/skills/obsidian-note-createPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Obsidian Note Create <purpose> Creating an Obsidian note isn't just writing a markdown file. It's frontmatter with the right properties, in the right folder, following the right template, with wikilinks to related notes. Get any of that wrong and the note is an orphan that doesn't show up in bases, has wrong metadata, or breaks linking conventions. This skill ensures notes are created correctly every time. </purpose> ## When To Activate <triggers> - User says "create note", "new note", "add note" - User says "add to obsidian", "save to vault" - User says "make a note about..." - Creating a .md file inside a known Obsidian vault - After granola-sync, research, or any skill that produces note-worthy output </triggers> Do NOT trigger for: - Editing existing notes (just edit them directly) - Non-Obsidian markdown files - Files outside a vault ## Instructions ### Step 1: Read Vault Conventions <conventions> Before creating anything, check for context: ```bash # Read vault map cat "$VAULT_PATH/CLAUDE.md" 2>/dev/null # If no CLAUDE.md, detect conventions from existing notes find "$VAULT_PATH" -name "*.md" -maxdepth 2 | head -20 head -20 "$VAULT_PATH"/<some-existing-note>.md # check frontmatter pattern ``` Extract: - Folder structure (where does this type of note go?) - Frontmatter schema (what properties are used?) - Template for this note type - Naming convention - Tag conventions If no CLAUDE.md exists and vault looks unstructured, suggest running
Details
- Skill name
obsidian-note-create- Repository
- ElliotJLT/Claude-Skill-Potions
- Path
skills/obsidian-note-create/SKILL.md- License
- MIT
- Repo updated
- 12 February 2026
FAQ
What does the Obsidian Note Create skill do?
Creates well-structured Obsidian notes with proper frontmatter, wikilinks, and template adherence. Detects available CLI (official, Yakitrak, or direct file write) and uses the best option. Reads vault conventions from CLAUDE.md before creating. Activates on "create note", "new note", "add to obsidian", or when creating markdown files in an Obsidian vault.
How do I install the Obsidian Note Create skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill obsidian-note-create. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Obsidian Note Create popular?
It lives in ElliotJLT/Claude-Skill-Potions, which has 62 GitHub stars and 2 forks.
Related skills
Agent Audit
62ElliotJLT/Claude-Skill-Potions
When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.
Battle Plan
62ElliotJLT/Claude-Skill-Potions
Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.
Breadcrumbs
62ElliotJLT/Claude-Skill-Potions
Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.
Obsidian Session Sync
62ElliotJLT/Claude-Skill-Potions
End-of-session ritual that syncs Claude Code session artifacts to an Obsidian vault. Chains breadcrumbs, retrospective, note creation, and daily driver into a single flow. Creates session notes, updates daily note, and leaves breadcrumbs. Activates on "sync to obsidian", "save session", "end session", or when user wraps up significant work in a vault-connected project.
Obsidian Daily Driver
62ElliotJLT/Claude-Skill-Potions
Manages daily notes workflow in Obsidian. Appends tasks, session logs, and learnings to today's daily note. Creates the daily note if it doesn't exist. Bridges Claude Code sessions to your daily note so nothing gets lost. Activates on "add to daily", "log this", "daily note", or end of session when daily notes are enabled.
Obsidian Vault Init
62ElliotJLT/Claude-Skill-Potions
Initialises an Obsidian vault for Claude Code workflows. Sets up folder structure, frontmatter conventions, templates, starter .base views, and a CLAUDE.md that describes the vault so future sessions understand it instantly. Activates on "set up obsidian", "init vault", "new vault", or first contact with an Obsidian project that has no CLAUDE.md.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.