obsidian-ontology-sync

To build a knowledge graph from Obsidian notes, this Skill extracts entities like Person, Organization, and Project, plus relationships like works_at or assigned_to, writing the structured data into a machine-queryable graph.jsonl file via upsert and relate operations.

Synchronization works by applying a YAML-configured workflow that parses Markdown notes, upserts extracted entities, creates relations, and outputs a machine-queryable graph.jsonl. This keeps your human-readable Obsidian notes and structured ontology consistently aligned.

Yes, you can automate Obsidian knowledge graph extraction using cron-based scheduling. This enables regular, hands-off synchronization to keep your ontology up to date with your latest Markdown notes for continuous personal knowledge management.

Yes, YAML configuration is required to define the extraction workflow. You initialize the config to specify how entities and relationships are parsed from Markdown notes, then run a dry-run extraction before enabling automatic syncing to the graph.jsonl file.

The best way to improve Obsidian note structure is to use analysis and feedback generated from your extracted ontology data. By evaluating the machine-queryable graph, you can identify gaps and refine your PKM templates and overall note organization.

Synchronizing Obsidian notes with a structured ontology depends on consistent Markdown formatting to accurately extract entities and relationships. Complex or unstructured notes may limit the effectiveness of building a machine-queryable knowledge graph.