add-frontmatter

Standardize and augment YAML frontmatter across Obsidian notes.

2.6k|194|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/heyitsnoah/claudesidian --skill add-frontmatter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-frontmatter
Source: https://github.com/heyitsnoah/claudesidian/tree/main/.agents/skills/add-frontmatter
Command: npx skills add https://github.com/heyitsnoah/claudesidian --skill add-frontmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add and standardize YAML frontmatter across Obsidian notes to improve organization, searchability, and consistency of metadata.

Core Features & Use Cases

  • Analyze notes to detect topics, note type (meeting, daily, reference, project) and relevant entities.
  • Generate, merge, and normalize frontmatter properties without duplicating existing valid data.
  • Migrate deprecated keys (tag -> tags, alias -> aliases, cssclass -> cssclasses) and ensure valid YAML syntax.
  • Apply changes in single files or folders, preserving original content and improving discoverability.

Quick Start

Run the add-frontmatter skill on a file or folder to automatically generate and merge YAML frontmatter according to note type.

Frequently Asked Questions about add-frontmatter

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

FAQPage Schema
How do I add YAML frontmatter to multiple Obsidian notes at once?

You can add YAML frontmatter to multiple Obsidian notes by running an automated skill on a folder, which analyzes note content and inserts consistent metadata across all files. It processes single files or entire folders, detecting note types like meeting, daily, reference, or project to apply relevant properties.

Can I update existing frontmatter without losing valid metadata?

Updating existing frontmatter preserves valid properties while merging new metadata. The skill analyzes current YAML syntax, keeps existing valid data intact, migrates deprecated keys like tag to tags or alias to aliases, and normalizes the structure to ensure consistency without duplicating values.

What is the best way to standardize YAML metadata tags across an Obsidian vault?

Standardizing YAML metadata across an Obsidian vault is best handled by an automated tool that detects note types, migrates deprecated keys like cssclass to cssclasses, and ensures valid YAML syntax. This process improves organization and searchability by applying consistent metadata structure vault-wide.

Does this frontmatter automation detect specific note types like meetings or daily logs?

Yes, frontmatter automation detects note types including meeting, daily, reference, and project by analyzing content. It then generates and applies relevant metadata properties based on the detected type, ensuring the YAML frontmatter accurately reflects the nature of each note.

How do I migrate deprecated frontmatter keys like tag to tags in Obsidian?

Migrating deprecated frontmatter keys like tag to tags, alias to aliases, and cssclass to cssclasses is handled automatically during the metadata update process. The skill scans your notes, replaces outdated keys with the correct pluralized versions, and ensures the resulting YAML remains syntactically valid.