メニュー
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".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use Firecrawl for markdown-first web scraping, crawling, and site mapping. Use when: "firecrawl", "crawl docs", "scrape website to markdown", "map website", "rag crawl".
ThoughtMap pipeline, output interpretation, and MCP vector search tools. Use when: "thoughtmap", "thought clusters", "search thoughts", "what am I thinking about", "semantic search notes", "knowledge base", "vector search", "find context in notes", "cluster distances", "topic map", "thinking patterns".
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, and properties. Also supports plugin and theme development. Use when the user asks to interact with their Obsidian vault from the command line, manage notes, search vault content, or develop and debug Obsidian plugins and themes.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
| name | obsidian-vault |
| description | 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". |
Conventions for working with this Obsidian vault. Every note should be findable, linkable, and useful months later.
| Topic | File | Use When |
|---|---|---|
| Vault structure | references/vault-structure.md | Navigating directories, creating notes |
| Frontmatter | references/frontmatter.md | Adding metadata to notes |
| Tags | references/tags.md | Organizing, searching by tag |
| Tasks | references/tasks.md | Obsidian Tasks plugin syntax |
| Wiki links | references/wiki-links.md | Linking between notes |
Utility scripts for vault analysis:
| Script | Purpose | Example |
|---|---|---|
| scripts/scan_tags.py | Find all tags | python .github/skills/obsidian-vault/scripts/scan_tags.py |
| scripts/scan_tasks.py | Find all tasks | python .github/skills/obsidian-vault/scripts/scan_tasks.py --pending |
YYYY-MM-DD.md → 2026-01-20.mdYYYY-Www.md → 2026-W03.mdYYYYMMDD meeting-topic.mdYYYYMMDD_event_name_YYYYMMDD.md (start_end dates)---
type: daily | project | meeting | note
status: active | done | paused | idea
tags: [type/daily, project/name]
created: YYYY-MM-DD
updated: YYYY-MM-DD
---
Tags can be hierarchical (project/myproject) or simple (#myproject).
Common prefixes: type/, status/, project/, area/
# By project tag
grep_search "project-name"
# Pending tasks with due dates
grep_search "- \[ \].*📅"
# Find all notes of a type
grep_search "type: meeting"
| 📅 Due | 🛫 Start | 🔺 Highest | ⏫ High | 🔼 Medium | 🔽 Low |
The vault is a knowledge base, not a filing cabinet. Every note should connect to something.
| Signal | Action |
|---|---|
| A topic grows beyond 2-3 paragraphs in a daily log | Extract to its own note |
| A recurring pattern emerges across sessions | Document it in the relevant project or skill |
| A decision has lasting impact | Record it in CONTEXT.md or a dedicated decision note |
| Research spans multiple sources | Create a synthesis note |
| You explain the same thing twice | Write it once, link to it |
Link, don't duplicate. If information exists elsewhere, use a [[wiki link]] to it.
Worked on [[Project/CONTEXT]]See [[2026-01-20]] for discussionTask assigned, tracked in [[Project/CONTEXT]]One note, one purpose. If a note covers two distinct topics, split it.
Notes are living documents. When a note gets messy or outdated, refactor it. Don't just keep appending.
Load reference files for detailed documentation on any specific topic.