Obsidian Ontology Sync

**Judgement** A well-conceived, domain-focused sync layer that turns an Obsidian vault into a queryable ontology with automated analytics and feedback. It’s particularly strong if your vault already follows (or can be adapted to) its opinionated folder and template conventions for contacts, clients, team, projects, and daily-status notes. **Strengths** - Automatic extraction of entities and relationships from markdown (contacts, clients, team, projects, daily logs). - Integrated analysis and feedback phases that surface missing info, broken links, relationship insights, and template improvements. - Cron-based scheduling for continuous sync, daily insights, and weekly feedback, with logs and dry-run options. - Local-first design: operates on your filesystem, writes ontology to separate storage (JSONL or sqlite), and emphasizes backups before applying changes. **Key Risks / Limitations** - Extraction rules are pattern- and path-based; if your Obsidian structure or note formats differ significantly, you may get incomplete or incorrect entities/relations until you adapt templates and folders. - The `apply-feedback` (bidirectional) phase can modify notes; while backups are promised, bugs or misconfigurations could still introduce unwanted edits or clutter. - Performance and robustness for very large vaults or complex custom schemas are not clearly characterized; expect some tuning and validation on first deployment. **Recommended Scenarios** - You are comfortable with the command line, cron, and basic YAML, and your main workspace is an Obsidian vault used for contacts, projects, and daily logs. - You want structured, queryable insight (e.g., who’s on which project, which contacts lack follow-up, workload distribution) without moving away from free-form markdown. - You’re willing to standardize some templates and folder layouts and to periodically review extraction results/feedback to calibrate the ontology. **Less Ideal If** - You are a non-technical Obsidian user who does not want to touch cron, configs, or CLIs. - Your vault has highly idiosyncratic structures and you’re unwilling to adjust templates to match the skill’s expectations. - You require strong guarantees around data modeling or complex, custom ontologies beyond the supported entities/relationships without investing in customization and testing.