kb-sync

Name: kb-sync
Availability: InStock
Author: webdevcom01-cell

Sync Obsidian vault documents with Agent Studio knowledge bases using contentHash change detection.

3|3|Updated Mar 5, 2026

Search Tags:#automation #obsidian #data-integrity #hashing #knowledge-base #kb-sync

Ready to run

npx skills add https://github.com/webdevcom01-cell/agent-studio --skill kb-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kb-sync
Source: https://github.com/webdevcom01-cell/agent-studio/tree/main/skills/kb-sync
Command: npx skills add https://github.com/webdevcom01-cell/agent-studio --skill kb-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the synchronization between Obsidian vault files and Agent Studio knowledge bases, ensuring KBs reflect the latest vault content with minimal manual effort.

Core Features & Use Cases

True-Sync workflow: ADD new documents, wait for READY, then DELETE old versions to prevent KB gaps.
Change detection by contentHash: only re-ingest files whose Obsidian content differs from the stored hash.
Robust per-agent operation: handles rate limiting, per-document polling, and multi-agent synchronization.

Quick Start

Run a full vault-to-KB sync to ingest changed Obsidian notes into each agent's knowledge base.

Frequently Asked Questions about kb-sync

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

FAQPage Schema

How do I sync Obsidian vault documents with agent knowledge bases?▼

To sync Obsidian vault documents with agent knowledge bases, this Skill compares Obsidian file hashes to stored content hashes and incrementally ingests changed files while preserving existing knowledge.

How does content hashing work for knowledge base updates?▼

Change detection by content hashing compares Obsidian file content against the stored hash, ensuring only modified documents are re-ingested into the agent knowledge base to minimize unnecessary updates.

How to prevent knowledge gaps when updating agent memory files?▼

To prevent knowledge gaps during updates, it uses a true-sync workflow that adds new documents, waits for READY status, and only then deletes old versions to maintain continuous knowledge availability.

Can I synchronize Obsidian notes across multiple SOMA agents?▼

Yes, this Skill operates across all configured SOMA agents, performing robust multi-agent synchronization with per-document polling and rate-limit safeguards to ensure reliable incremental ingestion.

Does syncing Obsidian files to Agent Studio handle API rate limiting?▼

Yes, syncing Obsidian files to Agent Studio includes built-in rate-limit safeguards and per-document polling to manage ingestion safely across all configured agents without exceeding limits.

Why does my knowledge base still show old documents during vault sync?▼

During vault sync, old documents remain visible until the new version reaches READY status, ensuring no knowledge gaps occur while the incremental ingestion process completes safely.