x-sync

Automate .xm/ project state synchronization across machines via a Bun HTTP server and SQLite database.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/x-mesh/x-kit --skill x-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-sync
Source: https://github.com/x-mesh/x-kit/tree/main/x-kit/skills/sync
Command: npx skills add https://github.com/x-mesh/x-kit --skill x-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the synchronization of .xm/ project state across multiple machines, ensuring consistency and collaboration without manual intervention.

Core Features & Use Cases

  • Server Management: Start, stop, and check the status of the sync server.
  • State Push/Pull: Push and pull project state (traces, plans, build data) between machines.
  • Setup Wizard: Configure sync credentials through an interactive setup process.
  • Status Overview: Provide a quick overview of the sync configuration and last sync state.
  • Use Case: Ideal for teams working on .xm/ projects that need to share and synchronize their work across different machines.

Quick Start

Set up the sync credentials and start the sync server. Then, use the /xm:sync push command to synchronize your project state.

Frequently Asked Questions about x-sync

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

FAQPage Schema
How do I synchronize project state across multiple machines?

Project state synchronization across multiple machines is handled by pushing and pulling .xm/ trace, plan, and build data via a lightweight Bun HTTP server backed by a SQLite database. You configure credentials, start the server, and run push or pull commands.

What is the best way to set up a SQLite sync server for project state?

The best way to set up a SQLite sync server is using the interactive setup wizard to configure credentials, then starting the lightweight Bun HTTP server. Once active, you can check its status and begin transferring project state.

Does project synchronization work without an active sync server?

No, project synchronization requires an active sync server and configured credentials to function. The server uses a lightweight Bun HTTP framework and SQLite database to manage and transfer the .xm/ project state.

Can I share build data and traces between different machines automatically?

Yes, you can share build data and traces between machines by running the push and pull commands against the sync server. This automates the transfer of .xm/ project state, ensuring consistency across different machines without manual intervention.

How do I troubleshoot sync configuration and check the last sync state?

You can troubleshoot sync configuration by requesting a status overview, which provides a quick summary of your current setup and the last sync state. Ensure your sync server is running and credentials are properly configured.

What are the limitations of using a lightweight HTTP server for machine state synchronization?

Using a lightweight HTTP server with SQLite for machine state synchronization is ideal for team collaboration on .xm/ projects, but requires the server to be actively running. State transfer depends on network availability and proper credential configuration.