obsidian-people

Create structured notes for people, creators, and organizations in Obsidian vault directories.

4|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/flowing-abyss/obsidian-vault-skills --skill obsidian-people
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-people
Source: https://github.com/flowing-abyss/obsidian-vault-skills/tree/main/skills/obsidian-people
Command: npx skills add https://github.com/flowing-abyss/obsidian-vault-skills --skill obsidian-people

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create notes for people, creators, and organizations in three directories (base/contacts/, base/creators/, base/productions/) with consistent structure, naming, and tagging to streamline vault organization and discovery.

Core Features & Use Cases

  • Three note types share identical structure but live in separate directories.
  • Enforces Title Case naming and a uniform frontmatter template with tags, aliases, categories, and metadata references.
  • Provides a clear linking workflow that only links to existing notes via the vault structure and supports category/meta/problem references when relevant.

Quick Start

Invoke by saying a trigger like "create contact" or "new author" to generate a new note in the appropriate base/ directory.

Frequently Asked Questions about obsidian-people

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

FAQPage Schema
How do I create structured notes for contacts and creators in an Obsidian vault?

To create structured notes for contacts and creators in an Obsidian vault, use triggers like "create contact" or "new author" to automatically generate notes with uniform frontmatter, title case filenames, and categorized tags in designated base directories.

Can I enforce consistent frontmatter and linking when generating organization notes in Obsidian?

Yes, you can enforce consistent frontmatter and linking when generating organization notes in Obsidian. The workflow requires a frontmatter template with name and description, and it strictly enforces linking only to existing notes via the vault structure.

What is the best way to organize people notes across different base directories in Obsidian?

The best way to organize people notes across different base directories in Obsidian is to separate contacts, creators, and productions into distinct folders while applying identical note structures, uniform tagging, and title case filenames for streamlined discovery.

Do I need a specific directory structure to automate contact note creation in Obsidian?

Yes, you need a specific directory structure to automate contact note creation in Obsidian. Your vault must contain base/contacts/, base/creators/, and base/productions/ directories to correctly route and store the generated notes based on the trigger action.

Are there limitations on linking to non-existent notes when generating creator notes in Obsidian?

Yes, there are limitations on linking when generating creator notes in Obsidian: the workflow strictly enforces linking exclusively to existing notes within the vault structure, preventing the creation of broken or placeholder links to non-existent files.