Obsidian Notes
If $ARGUMENTS is provided, treat it as the user's note request and proceed directly without asking for clarification.
Overview
Standard operations for reading, writing, and organizing notes in the Obsidian vault (Obsidian Flavored Markdown with YAML frontmatter and wikilinks). All vault operations use Obsidian MCP tools with vault-relative paths.
Companion Skills
Obsidian supports more than plain markdown notes. Before proceeding, consider whether the user's request is better served by one of these formats:
| Skill |
Format |
When to use |
obsidian-markdown |
.md |
Always invoke when creating or editing notes — ensures correct Obsidian Flavored Markdown (wikilinks, callouts, embeds, properties) |
obsidian-bases |
.base |
User wants a database view, filtered table, card gallery, or summary of notes by properties |
json-canvas |
.canvas |
User wants a visual layout — mind map, flowchart, project board, or spatial arrangement of ideas |
Invoke the relevant skill(s) before writing content so you follow the correct syntax.
Directory Structure
Top-level categories: Work/, Dev/, Games/, Personal/, Travel/, DailyNote/
- Max depth: 3 levels for general notes
- Exception: Projects and Meetings allow 4 levels
Special Note Types (use templates)
| Type |
Path pattern |
Template |
| Project |
Work/Projects/[ProjectName]/[ProjectName].md |
assets/project.md |
| Meeting |
Work/Meetings/YYYY/MM/[title] YYYY-MM-DD.md |
assets/meeting.md |
| DailyNote |
DailyNote/YYYY/MM/YYYY-MM-DD.md |
Use get_periodic_note, append_periodic_note, patch_periodic_note |
Note Creation Checklist
- Determine note type (project / meeting / daily / general)
- Select template if applicable
- Create with
create_note(path, content)
- Verify frontmatter fields:
title, created, updated, tags
- Verify creation:
read_note(path) to confirm file was created and YAML is valid
Reference Files
| File |
When to read |
references/note-organization.md |
Naming, tag system, frontmatter standards |
references/tool-selection.md |
Unsure which tool to use |
references/error-handling.md |
File not found, YAML errors, search returns nothing |
references/meeting-workflow.md |
Any meeting note operation (create, query, update status) |
references/project-workflow.md |
Any project note operation (query, create, update, Jira integration) |
1---2name: writing-note3description: Use this skill to read, write, search, or modify files in the user's local Obsidian vault (markdown notes). This is the user's personal knowledge base stored as local files. Trigger whenever the request involves personal notes — including "save this to my notes", "幫我記", "幫我存", "daily note", "筆記", "幫我找...筆記", "我之前有存", "更新筆記", "meeting note", "project note", or appending entries to today's log. This skill is the default for any request to persist, retrieve, or edit personal knowledge when no external service (Jira, GitHub, Confluence, Linear, Things, Slack, email) is explicitly specified. Also trigger on any mention of "Obsidian", "vault", or "my notes".4---5
6# Obsidian Notes
7
8If `$ARGUMENTS` is provided, treat it as the user's note request and proceed directly without asking for clarification.
9
10## Overview
11
12Standard operations for reading, writing, and organizing notes in the Obsidian vault (Obsidian Flavored Markdown with YAML frontmatter and wikilinks). All vault operations use Obsidian MCP tools with vault-relative paths.
13
14## Companion Skills
15
16Obsidian supports more than plain markdown notes. Before proceeding, consider whether the user's request is better served by one of these formats:
17
18| Skill | Format | When to use |
19|-------|--------|-------------|
20| `obsidian-markdown` | `.md` | **Always invoke** when creating or editing notes — ensures correct Obsidian Flavored Markdown (wikilinks, callouts, embeds, properties) |
21| `obsidian-bases` | `.base` | User wants a database view, filtered table, card gallery, or summary of notes by properties |
22| `json-canvas` | `.canvas` | User wants a visual layout — mind map, flowchart, project board, or spatial arrangement of ideas |
23
24Invoke the relevant skill(s) before writing content so you follow the correct syntax.
25
26## Directory Structure
27
28Top-level categories: `Work/`, `Dev/`, `Games/`, `Personal/`, `Travel/`, `DailyNote/`
29
30- Max depth: **3 levels** for general notes
31- Exception: Projects and Meetings allow **4 levels**
32
33## Special Note Types (use templates)
34
35| Type | Path pattern | Template |
36|------|-------------|----------|
37| Project | `Work/Projects/[ProjectName]/[ProjectName].md` | `assets/project.md` |
38| Meeting | `Work/Meetings/YYYY/MM/[title] YYYY-MM-DD.md` | `assets/meeting.md` |
39| DailyNote | `DailyNote/YYYY/MM/YYYY-MM-DD.md` | Use `get_periodic_note`, `append_periodic_note`, `patch_periodic_note` |
40
41## Note Creation Checklist
42
431. Determine note type (project / meeting / daily / general)
442. Select template if applicable
453. Create with `create_note(path, content)`
464. Verify frontmatter fields: `title`, `created`, `updated`, `tags`
475. Verify creation: `read_note(path)` to confirm file was created and YAML is valid
48
49## Reference Files
50
51| File | When to read |
52|------|-------------|
53| `references/note-organization.md` | Naming, tag system, frontmatter standards |
54| `references/tool-selection.md` | Unsure which tool to use |
55| `references/error-handling.md` | File not found, YAML errors, search returns nothing |
56| `references/meeting-workflow.md` | Any meeting note operation (create, query, update status) |
57| `references/project-workflow.md` | Any project note operation (query, create, update, Jira integration) |
majiayu000