Obsidian Ontology Sync

v1.0.0

Bidirectional sync between Obsidian PKM (human-friendly notes) and structured ontology (machine-queryable graph). Automatically extracts entities and relatio...

0· 40·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Obsidian ⇄ ontology sync) match the included instructions and the Python sync.py: it scans a vault, parses markdown, extracts entities/relations and writes them to a local ontology file. There are no unrelated credentials, binaries, or external services declared.
Instruction Scope
Instructions and the script operate on the user's Obsidian vault (configured vault_path) and write append-only graph entries to a local storage path. This is coherent for the feature, but the script extracts PII fields (emails, phone numbers, company names, project links) and writes them into a graph.jsonl file — so it collects and centralizes sensitive personal data from any files under the scanned paths. There are no network calls in the provided code, so extraction appears local-only.
Install Mechanism
This is instruction-only with a bundled Python script; there is no install spec, no remote downloads, and no package installation instructions. Risk from install mechanism is minimal.
Credentials
The skill declares no required env vars or credentials and the code does not attempt to read secrets or external service tokens. That is proportional to a local file-parsing sync tool. Note: the script looks for config files in several default paths (including user-specific paths), and the provided config.yaml points to a specific Windows user path — ensure it is updated to your vault path before running.
Persistence & Privilege
The skill does not request always:true and does not modify other skills. It creates/updates a local ontology file (append to graph.jsonl) and network autonomy is allowed by platform defaults but the code itself performs only local file I/O. The append-only write behavior can accumulate old/removed data over time.
Assessment
This skill appears to do what it claims: parse your Obsidian vault and build a local ontology. Before installing or running it, check the following: 1) Update config.yaml to point to your actual vault and desired ontology storage path; the bundled config references a specific user path (C:\Users\shenz\...) which you should not use as-is. 2) Understand privacy implications: the script extracts emails, phones, companies and other personal data and writes them into an append-only graph.jsonl in the configured storage directory — review that file and protect it (permissions, backups). 3) The code currently writes by appending, so deleted/changed data may persist in the ontology file; consider rotating or truncating the storage file if desired. 4) There are no network calls in the provided script, but always inspect future updates for outbound network code before running. 5) There are minor metadata inconsistencies (pack metadata/owner/version differences in _meta.json vs registry) — not inherently dangerous but a signal to prefer skills with a known source or homepage. If you plan to run this automatically (cron/agent), ensure the storage path is secure and you are comfortable with automated extraction of potentially sensitive notes.

Like a lobster shell, security has layers — review code before you run it.

latestvk97669z1n8jnjaz8d4aeg97dt9840spj

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments