agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer
Profile →npx skills add ruvnet/ruflo --skill agent-crdt-synchronizer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Implements Conflict-free Replicated Data Types for eventually consistent distributed state synchronization. It supports state-based CRDTs, operation-based CRDTs, delta synchronization, conflict resolution, and causal consistency. It exposes a high-priority synchronizer that initializes CRDT state tracking, prepares delta state computation, and validates conflict-free convergence after synchronization.
How it works
The skill describes a base CRDT framework and concrete CRDT implementations (G-Counter, OR-Set, LWW-Register, OR-Map, RGA) plus a Delta-State CRDT framework. Core actions include:
- Register CRDT instances, creating specific CRDT types via createCRDTInstance.
- Maintain a vector clock, deltaBuffer, and sync scheduler for coordination.
- Synchronize with peers by building a CRDT_SYNC_REQUEST containing sender, vectorClock, local state, and deltas, then processing the response via processSyncResponse.
- Each CRDT type includes typical operations: increment for G-Counter, add/remove/has/values for OR-Set, set/merge for LWW-Register, insert/remove/merge for RGA, and delta tracking for updates.
- Delta tracking: observe updates via onUpdate and notify via delta events, storing deltas with timestamps and vector clocks.
- Delta-state framework: apply operations, compute deltas, buffer deltas, and provide deltas since last sync for a peer.
The code snippets outline concrete classes and methods, including CRDTSynchronizer, GCounter, ORSet, LWWRegister, RGA, and DeltaStateCRDT, with behaviors for state merging, updates, and synchronization flows. The pre/post hooks print status messages during synchronization.
When to use it
Use this skill when you need distributed state synchronization across nodes with CRDT guarantees. It is intended for scenarios requiring:
- eventual consistency through CRDTs
- delta-based synchronization to minimize bandwidth
- deterministic conflict resolution
- causal ordering of operations
What it can touch
It interacts with several components and concepts:
- CRDT instances registered via registerCRDT(name, crdtType, initialState)
- CRDT types such as 'G_COUNTER', 'PN_COUNTER', 'OR_SET', 'LWW_REGISTER', 'OR_MAP', 'RGA' as per createCRDTInstance
- Peer communication via synchronize and synchronizeWithPeer, using messages like CRDT_SYNC_REQUEST containing vectorClock, state, and deltas
- Deltas tracked through update callbacks registered with onUpdate
Caveats
The skill describes a partial, illustrative implementation with placeholder logic for complex CRDT merging and ordering. It notes high-level behavior and includes example implementations but may require integration work to ensure production-ready correctness, network transport, and complete delta computation semantics. License is MIT. No explicit runtime constraints or platform requirements are stated beyond the code structure and tool compatibility (claude-code, codex).
--- name: crdt-synchronizer type: synchronizer color: "#4CAF50" description: Implements Conflict-free Replicated Data Types for eventually consistent state synchronization capabilities: - state_based_crdts - operation_based_crdts - delta_synchronization - conflict_resolution - causal_consistency priority: high hooks: pre: | echo "🔄 CRDT Synchronizer syncing: $TASK" # Initialize CRDT state tracking if [[ "$TASK" == *"synchronization"* ]]; then echo "📊 Preparing delta state computation" fi post: | echo "🎯 CRDT synchronization complete" # Verify eventual consistency echo "✅ Validating conflict-free state convergence" --- # CRDT Synchronizer Implements Conflict-free Replicated Data Types for eventually consistent distributed state synchronization. ## Core Responsibilities 1. **CRDT Implementation**: Deploy state-based and operation-based conflict-free data types 2. **Data Structure Management**: Handle counters, sets, registers, and composite structures 3. **Delta Synchronization**: Implement efficient incremental state updates 4. **Conflict Resolution**: Ensure deterministic conflict-free merge operations 5. **Causal Consistency**: Maintain proper ordering of causally related opera
- Core Responsibilities
- Technical Implementation
- Base CRDT Framework
- G-Counter Implementation
- OR-Set Implementation
- LWW-Register Implementation
- RGA (Replicated Growable Array) Implementation
- Delta-State CRDT Framework
- MCP Integration Hooks
- Memory Coordination for CRDT State
- Performance Monitoring
- Advanced CRDT Features
- Causal Consistency Tracker
- CRDT Composition Framework
What does the agent-crdt-synchronizer skill do?
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer
How do I install it?
Run `npx skills add ruvnet/ruflo --skill agent-crdt-synchronizer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.