// Audit all notes in the Awesome Search Obsidian vault for missing or incomplete frontmatter. Reports violations by folder and optionally auto-fixes notes where values can be inferred from content. Use for KG consistency checks.
Build and maintain a dense semantic knowledge graph about search and IR inside an Obsidian vault. Triggers on article URLs, article titles or names (from Clippings/, raw_articles/, or unprocessed vault notes), and requests to enrich or reprocess existing notes for concepts, people, companies, tools, or topics.
Find disconnected clusters in the Awesome Search Obsidian vault — groups of notes that are internally linked but isolated from the rest of the graph. Identify semantic overlap between clusters and suggest bridge links. Use for deep graph connectivity audits.
Audit hub notes in the Awesome Search Obsidian vault — rank notes by inbound link count and compare against existing Topics/ notes. Surfaces mismatches where high-traffic concepts lack a proper topic page. Use for periodic graph structure reviews.
Find orphan notes in the Awesome Search Obsidian vault — notes with no wikilinks in or out — and suggest or apply connections to existing notes. Use when running a graph health audit or when the KG feels sparse.
| name | awesome-search-kg-frontmatter |
| description | Audit all notes in the Awesome Search Obsidian vault for missing or incomplete frontmatter. Reports violations by folder and optionally auto-fixes notes where values can be inferred from content. Use for KG consistency checks. |
Use this skill to check all notes for required frontmatter fields and fix missing values where they can be inferred from content.
| Type | Required fields |
|---|---|
article | type, title, source, author, created, tags, concepts |
concept | type, tags, created |
topic | type, tags, related_concepts, created |
person | type, tags, created |
company | type, tags, created, website (if known) |
tool | type, tags, created, website or repo (if known) |
Always use the Obsidian MCP server for all vault operations — never access the vault directly via the filesystem (no Read/Write/Bash file tools). The MCP server is the only sanctioned way to read, search, create, and edit notes.
Check every note in Awesome Search/ for:
type fieldcreated fieldsource field (articles only)tags fieldconcepts or related_concepts (articles and topics)type: article but no authorFRONTMATTER AUDIT REPORT
========================
Articles/ — N notes, N violations:
Missing `source`: [list of note names]
Missing `author`: [list]
Missing `concepts`: [list]
Concepts/ — N notes, N violations:
Missing `type`: [list]
Missing `created`: [list]
People/ — N notes, N violations:
...
Total violations: N across N notes
For each violation, attempt to infer the missing value from note content:
type: infer from folder (Articles/ → article, Concepts/ → concept, etc.)created: use file creation date if available, otherwise 2026-05-17tags: infer from folder and note contentauthor: look for **Author:** or **Source:** lines in the note bodysource: look for URLs in the note bodyAsk for confirmation before writing, or auto-fix if the user has approved batch mode.
For fields that cannot be reliably inferred (e.g. concepts for an article with no entity extraction yet), flag the note for manual review:
NEEDS MANUAL REVIEW
===================
- Articles/Some Article.md — missing `concepts` (no entity extraction done)
- People/Some Person.md — missing `website` (could not find URL in note)
FIX SUMMARY
===========
Auto-fixed: N fields across N notes
Flagged for manual review: N notes
No action needed: N notes
awesome-search-kg-orphans — orphan detection is more reliable with consistent type fieldsClippings/ and raw_articles/ are exempt — they are pre-processing staging areas, not KG notes