electricsql

Synchronize PostgreSQL data with client applications via ElectricSQL Shapes.

14|5|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/oakoss/agent-skills --skill electricsql
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: electricsql
Source: https://github.com/oakoss/agent-skills/tree/main/skills/electricsql
Command: npx skills add https://github.com/oakoss/agent-skills --skill electricsql

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of keeping client-side data synchronized in real-time with a PostgreSQL database, enabling robust local-first application architectures.

Core Features & Use Cases

  • Real-time Sync: Streams partial replicas of Postgres data to clients using ElectricSQL's Shape technology.
  • Offline Support: Enables applications to function seamlessly offline by maintaining a local data replica.
  • Efficient Data Replication: Utilizes Shapes for partial replication, syncing only necessary data.
  • Use Case: Building a collaborative task management app where multiple users can edit tasks offline, and all changes sync automatically and in real-time once connectivity is restored.

Quick Start

Use the electricsql skill to set up real-time Postgres sync for your application.

Frequently Asked Questions about electricsql

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

FAQPage Schema
How do I sync PostgreSQL data to client apps in real-time?

PostgreSQL sync to clients is achieved by streaming partial replicas using ElectricSQL's Shape technology, ensuring data consistency across devices. This enables local-first application architectures with offline support and automatic conflict resolution.

What is partial data replication and how does it work for offline-first apps?

Partial data replication uses Shapes to sync only the necessary subset of Postgres data to the client. This allows offline-first apps to maintain a local data replica, function seamlessly without connectivity, and sync changes bidirectionally once online.

Can I build a local-first app that handles writes and syncs data when connectivity is restored?

Yes, local-first apps can handle offline writes and sync automatically using progressive write strategies. When connectivity is restored, bidirectional synchronization ensures all offline changes are persisted and reconciled with the PostgreSQL database.

Does this real-time sync approach work with existing PostgreSQL databases?

Yes, this real-time sync approach works directly with PostgreSQL databases to facilitate bidirectional data synchronization. It manages partial replication via Shapes and supports production patterns like auth proxies and robust error handling.

What are the limitations of using partial replication shapes for local-first data sync?

Using partial replication shapes requires careful management of data consistency and robust error handling for production deployments. You must plan auth proxies and progressive write strategies to handle complex offline edge cases effectively.