Skills Guide

Obsidian Vault Note Creation

VerifiedSafe

Create notes for Kyle's Obsidian vault following established conventions for frontmatter, taxonomy, and formatting.

Sby Skills Guide Bot
ProductivityIntermediate
007/23/2026
Claude Code
#obsidian#note-taking#knowledge-management#markdown

Recommended for

Claude CodeProduct managerBeginnerProductivitySolo / indie hacker

Our review

Creates Obsidian vault notes following strict frontmatter, tagging, placement, and formatting conventions to maintain a structured knowledge base.

Strengths

  • Ensures uniform consistency across all vault notes.
  • Enforces a controlled taxonomy, preventing ad-hoc tags.
  • Integrates pre-write CLI checks to improve linking and placement.
  • Provides clear rules for tables of contents and Obsidian callouts.

Limitations

  • Requires Obsidian to be running for full CLI-based pre-write checks.
  • Rigid taxonomy may not fit niche or interdisciplinary topics.
  • Assumes user adherence to conventions, which can be cumbersome.
When to use it

When adding a new note to an Obsidian vault that follows a specific organizational schema and taxonomy.

When not to use it

When writing a quick, informal note without regard for vault structure or when the note does not fit the defined taxonomy.

Security analysis

Safe
Quality score92/100

The skill instructs non-destructive shell commands (obsidian CLI for search, backlinks, file listing) with fallback to Glob/Grep. No sensitive data exfiltration, no disabling of safety features, no execution of remote or obfuscated payloads. The use of Bash is limited to these harmless operations.

No concerns found

Examples

Create a research note
Create a new research note on the topic of AI agents for marketing, dated today, with status active. Place it in the Research folder for this month.
Add a project note
Add a project note for the new website redesign project in the Projects folder, with tags [business, plan], and include a TOC if it has more than 3 sections.
Create a reference clipping
Create a reference note for a PDF about competitive analysis, placed in References/, with tags [research, business], and set status to active.

name: vault-note description: Create Obsidian vault notes with correct frontmatter, taxonomy, and formatting conventions allowed-tools: "Bash Read Write Edit Glob Grep"

Vault Note

Create notes for Kyle's Obsidian vault following all established conventions.

Frontmatter

Every note must include:

---
date: YYYY-MM-DD
tags:
  - <tag>
status: active | archive
aliases: []
---
  • date is the creation or last-major-edit date
  • tags must include at least one from the taxonomy
  • status is active for current notes, archive for completed/retired
  • aliases can be empty [] but the field must exist

Tag Taxonomy

Use only these tags: ai, tools, business, marketing, career, finance, strategy, plan, architecture, review, playbook, research, delightful, github, braze, rosetta, clipping, briefing, meta, audit

If a note doesn't fit cleanly, use the closest match. Don't invent new tags.

Placement Rules

| Content type | Location | |---|---| | Formal research — /research output or Kyle-authored | Research/<Month YYYY>/ | | Research-adjacent deliverables staging (not from /research) | Claude/Findings/<Month YYYY>/ | | Active project work | Projects/<project-name>/ | | Clippings, PDFs, external material | References/ | | Topic synthesis pages (wiki) | Wiki/ | | Completed/retired notes | Archive/ (set status: archive) |

Table of Contents

Notes with 4 or more ## sections must include a numbered TOC after the frontmatter using [[#Section]] wiki-links. Do NOT put numbers in section headers — numbering belongs in the TOC list only.

Pre-Write Vault Check (CLI)

Before writing a note, use the Obsidian CLI to improve placement and linking (requires Obsidian running — skip if unavailable):

  1. Find linking candidates — obsidian search query="<topic keywords>" limit=10 to discover notes worth wiki-linking
  2. Check for orphans — obsidian backlinks file="<similar note>" to see what links into related content and mirror those patterns
  3. Verify placement — obsidian files folder="<target folder>" to confirm the destination folder exists and see sibling notes

Fall back to Glob/Grep if the CLI is unavailable.

  1. Wiki relevance — If the note is tagged research, check Wiki/ for a topic page that should link to this note. Flag it for the user if a wiki update seems warranted. Do not auto-edit wiki pages from vault-note — that's the research skill's job or a manual session.

Formatting Conventions

  • Monolithic notes. Notes are long-form and heavily cross-referenced. Don't atomize.
  • Wiki-links are organic. Use [[note name]] and [[note name#section]] inline where contextually relevant. No forced ## Related appendix sections.
  • Obsidian callouts. Use [!note], [!tip], [!warning], [!danger], [!info], [!success], [!question], [!quote] sparingly — 1–3 per note max.
  • Footnotes for sources. Prefer footnotes over inline URLs when a sentence references a source.[^1] Inline URLs are fine in lists or when the link IS the content.
  • No inline #tags in runner/automated output. Inline tags are welcome in conversational notes.
  • Block quotes from previous outputs. When continuing or contradicting a previous note, pull it in with a wiki-linked block quote:

    From [[AI Briefing — 2026-02-27#News]]: Content from that note...

  • No loose files in vault root. Everything has a home.
Related skills

Task Prioritizer

Productivity

Prioritizes your tasks using Eisenhower, ICE, and RICE frameworks.

claudechatgptbeginner
241
67
719
Admin

Weekly Status Report Generator

Productivity

Generate structured and concise weekly status reports.

Claude CodeCursorWindsurf+1beginner
234
78
746
Admin

Daily Standup Report

Productivity

Generates structured and concise daily standup reports.

claudeCursorWindsurfbeginner
178
45
584
Admin