kg-frontmatter

Run the audit to scan every note in the vault against a required-fields table per note type. It reports missing fields like type, tags, created, source, and author grouped by folder, then optionally auto-fixes values it can infer.

The skill infers missing values from context: type from the folder, created from the file date, tags from folder and content, and author or source from lines in the note body. It asks for confirmation before writing unless batch mode is approved.

All notes require type, tags, and created. Articles additionally need source, author, and concepts; videos need speaker, url, and concepts; topics need related_concepts; case studies need companies, related_concepts, and source; tools and datasets need website or repo where known.

No. All vault operations go through the Obsidian MCP server, which is the only sanctioned way to read, search, create, and edit notes. Direct filesystem access via Read, Write, or Bash tools is explicitly disallowed.

Notes in Clippings/ and raw_articles/ are exempt because they are pre-processing staging areas rather than knowledge graph notes. All other folders such as Articles, Concepts, People, and Tools are fully scanned.

Fields that cannot be reliably inferred, such as concepts for an article with no entity extraction, are flagged in a manual review list. The summary reports how many fields were auto-fixed, how many notes need review, and how many required no action.