knowledge-sync

What This Skill Does

The Knowledge Sync skill is a robust infrastructure component for OpenClaw that automates the orchestration of your digital second brain. It bridges the gap between local development workspaces, server-side storage, and note-taking applications like Obsidian. By utilizing a multi-layered approach—combining inotifywait for real-time local file monitoring, automated Git version control, and cloud-native synchronization via Nutstore—it ensures that your information stays current, consistent, and accessible across multiple devices. The skill follows the core principle that "Text > Brain," prioritizing durable, syncable file formats over ephemeral local storage.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/alfredming-2026/knowledge-sync

After installation, you must configure the watch list to target your specific workspace directories. The skill utilizes a systemd service for background monitoring; execute systemctl --user enable sync-realtime.service to ensure the daemon starts upon login. For remote synchronization, configure your Git remotes (e.g., Gitee) to handle off-site backups, and ensure your git-auto-push.sh and git-auto-pull.sh scripts are correctly mapped in your Crontab as detailed in the technical documentation.

Use Cases

• Unified Knowledge Management: Sync your local Obsidian notes across your workstation and server environments.
• Automated Backup Cycles: Ensure that every markdown file saved in your articles/ or projects/ folder is pushed to a remote repository every 5 minutes.
• Cross-Platform Consistency: Keep a server-side workspace, a local Git repo, and cloud-synced storage (like Nutstore) in perfect parity for collaborative writing or coding.
• Reduced Operational Overhead: Automate conflict resolution and file updates so you can focus on content creation rather than manual file management.

Example Prompts

1. "OpenClaw, please enable the real-time knowledge sync service for my current projects directory."
2. "Check the status of my sync-realtime service and let me know if there are any outstanding merge conflicts in my knowledge base."
3. "Trigger a manual git-push for my notes to ensure my latest updates are backed up to Gitee immediately."

Tips & Limitations

• Frequency Control: While inotifywait provides near-instant updates, Git pushes are batch-processed every 5 minutes. Do not expect instantaneous global state consistency if you are alternating between machines rapidly.
• Conflict Management: Always pull before you push. The system is designed for individual knowledge maintenance; avoid concurrent edits to the same file from multiple devices to minimize conflict resolution overhead.
• Exclusions: Use the EXCLUDE_PATTERN configuration wisely. Do not track large build artifacts, log files, or temporary system files to keep your repository clean and fast.
• Monitoring: Keep an eye on the sync latency. If your synchronization exceeds 30 seconds, verify your systemd logs for file descriptor limits or disk I/O bottlenecks.