create-note

Convert Markdown files into Obsidian notes with frontmatter and daily note links.

7|3|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/seabbs/claude-code-config --skill create-note
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-note
Source: https://github.com/seabbs/claude-code-config/tree/main/skills/create-note
Command: npx skills add https://github.com/seabbs/claude-code-config --skill create-note

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically import and format scattered Markdown files into a consistent Obsidian note structure, saving time and ensuring frontmatter and cross-note links are correctly initialized.

Core Features & Use Cases

  • Import a Markdown file and format it as an Obsidian note with proper frontmatter.
  • Copy the note into the Obsidian vault and add a link from the daily note for easy navigation.
  • Rename notes safely using a sanitized, lowercase hyphenated filename pattern.

Quick Start

Use /create-note <source_markdown_path> [<target_name>] to import and format the note in your Obsidian vault.

Frequently Asked Questions about create-note

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import markdown files into an Obsidian vault with consistent frontmatter?

You can import markdown into an Obsidian vault by providing the source file path; the Skill derives a sanitized filename, copies the file to the vault, and updates the frontmatter for consistency.

Can I automatically link imported markdown notes from my Obsidian daily note?

Yes, you can link imported markdown notes by establishing a connection from the daily note. The Skill optionally accepts a target name to create this navigation link automatically during import.

Does importing markdown into Obsidian standardize the filenames and formatting?

Importing markdown into Obsidian standardizes formatting by applying consistent frontmatter and renaming files safely using a sanitized, lowercase hyphenated filename pattern to maintain vault structure.

What is the best way to centralize scattered markdown documents into one Obsidian vault?

The best way to centralize scattered markdown documents is using an automated import process that reads each source file, initializes frontmatter and cross-note links, and copies the formatted note into the vault.

Do I need to manually update frontmatter when adding markdown files to Obsidian?

No, you do not need to manually update frontmatter. The import process automatically reads the source markdown file and initializes the frontmatter to ensure all notes maintain a consistent structure.

How do I rename Obsidian notes safely when importing from external markdown sources?

To rename Obsidian notes safely during import, the process automatically derives a sanitized filename from the source markdown, converting it into a lowercase hyphenated pattern to prevent vault conflicts.