database-sync

Synchronize PostgreSQL, SQLite, and Redis with version-vector conflict resolution.

3|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/orchestra-mcp/framework --skill database-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-sync
Source: https://github.com/orchestra-mcp/framework/tree/main/.claude/skills/database-sync
Command: npx skills add https://github.com/orchestra-mcp/framework --skill database-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexities of managing data consistency across different database systems (PostgreSQL, SQLite, Redis) and ensures seamless offline support and real-time updates.

Core Features & Use Cases

  • Multi-database Strategy: Manages data flow between cloud PostgreSQL, local SQLite, and Redis for caching/pub-sub.
  • Sync Protocol: Implements robust push and pull mechanisms for data synchronization.
  • Conflict Resolution: Handles data conflicts using a last-write-wins strategy with version vectors.
  • Use Case: Ensure that user data entered offline in a mobile app is correctly merged with the central PostgreSQL database once the device is back online, resolving any potential conflicts.

Quick Start

Configure the database synchronization system for PostgreSQL, SQLite, and Redis.

Frequently Asked Questions about database-sync

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

FAQPage Schema
How do I synchronize data between PostgreSQL and SQLite for offline support?

Conflict resolution during data synchronization uses a last-write-wins strategy based on version vectors and timestamps, determining which data changes take precedence when merging offline SQLite entries with PostgreSQL.

Can I use Redis caching and pub/sub with my PostgreSQL sync workflow?

Database schema management supports GORM model patterns, providing migration commands to handle schema changes across PostgreSQL, SQLite, and Redis during the data synchronization setup process.

What is the best way to handle conflict resolution when syncing offline SQLite data?

Conflict resolution during data synchronization uses a last-write-wins strategy based on version vectors and timestamps, determining which data changes take precedence when merging offline SQLite entries with PostgreSQL.

Does the sync protocol support GORM model patterns and database schema migrations?

Database schema management supports GORM model patterns, providing migration commands to handle schema changes across PostgreSQL, SQLite, and Redis during the data synchronization setup process.