obsidian-ontology-sync

Obsidian ontology sync extracts entities and relationships from Markdown notes to automate bidirectional synchronization between your vault and a structured graph. It handles contacts, teams, projects, and events across references, daily-status, and projects notes using YAML-driven config and cron-based scheduling.

Knowledge graph extraction for Obsidian PKM parses Markdown notes to identify entities and relationships, preserving them in a file-based ontology store. It runs end-to-end extraction, analysis, and feedback phases to maintain a machine-queryable graph for cross-note analytics and consistency checks.

Yes, you can schedule automated ontology syncs for your Obsidian vault using the built-in cron-based scheduling. This automates the extraction, analysis, and feedback phases at a configured cadence, requiring only a YAML-driven config to target your specific notes.

Yes, PyYAML is the required dependency for managing the YAML-driven configuration that controls entity extraction and the file-based ontology store. You also need an accessible Obsidian vault containing your Markdown notes to begin syncing.

The best way to find data quality gaps in Obsidian notes is using the skill's feedback phase, which detects inconsistencies and suggests template improvements. This identifies missing entities or relationships, enhancing your personal knowledge management structure over time.

Obsidian notes lack a machine-queryable representation because standard Markdown stores text without structured entities or relationships. This skill solves the problem by extracting that data into a file-based ontology store, enabling cross-note analytics and consistency checks.