ontologian-sync

Synchronizes local ontology directory with global ~/.ologian store after preview and confirmation.

3|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/swszz/ontologian --skill ontologian-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontologian-sync
Source: https://github.com/swszz/ontologian/tree/main/plugin/skills/sync
Command: npx skills add https://github.com/swszz/ontologian --skill ontologian-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize the local ontology directory with the global store to ensure consistency across environments and enable centralized governance.

Core Features & Use Cases

  • Preview before syncing: Show a local-to-global diff prior to applying changes.
  • Controlled sync: Require explicit user confirmation before copying files to the global store.
  • Domain-wide coverage: Handle all domains defined in ontology/domains/_index.yaml and copy objects, links, and actions accordingly.

Quick Start

Run the Ontologian Sync command to preview and then confirm the sync to the global store.

Frequently Asked Questions about ontologian-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync my local ontology directory to a central store?

To sync your local ontology, run the sync command to trigger a workflow that discovers domains, renders a local-to-global diff preview, and copies files after user confirmation.

Can I preview changes before committing an ontology sync?

Yes, you can preview changes before committing an ontology sync because the workflow explicitly renders a local-to-global diff for your review and requires explicit confirmation before copying.

How does domain-wide ontology synchronization work for multiple domains?

Domain-wide ontology synchronization works by reading the domains/_index.yaml file to discover all defined domains and copying their associated objects, links, and actions to the global store.

Do I need to manually confirm before copying ontology files to the global store?

Yes, you need to manually confirm before copying ontology files because the workflow enforces a multi-step process requiring explicit user approval after the preview rendering step.

What is the best way to ensure ontology consistency across different environments?

The best way to ensure ontology consistency across environments is synchronizing your local ontology directory with the central global store to enable centralized governance.

Why does my ontology sync workflow require a multi-step process?

Your ontology sync workflow requires a multi-step process to enforce safe file operations by ensuring initialization, discovery, preview rendering, and confirmation occur before any files are copied.