tx-sync-data

Export, import, migrate, hydrate, and compact tx task state across SQLite and JSONL.

6|3|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/jamesaphoenix/tx --skill tx-sync-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tx-sync-data
Source: https://github.com/jamesaphoenix/tx/tree/main/.claude/skills/tx-sync-data
Command: npx skills add https://github.com/jamesaphoenix/tx --skill tx-sync-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

## What problem does it solve? This skill helps teams move and synchronize task state and related artifacts across storage formats, tools, and environments, reducing friction and data drift.

## Core Features & Use Cases

  • Cross-format data flow: export, import, migrate, hydrate, and compact task state and sync artifacts across SQLite, JSONL, Claude Code directories, and migration layers.
  • Lifecycle coordination: manage serial tasks like export, hydrate, and status checks to keep streams consistent.
  • Use Case: a Claude Code team member needs to push completed work to a shared log and rebuild state from events.

### Quick Start Run tx sync export to generate stream events, then tx sync hydrate to reconstruct the state from those events.

Frequently Asked Questions about tx-sync-data

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

FAQPage Schema
How do I export and migrate task state between SQLite and JSONL formats?

You can export and migrate task state between SQLite and JSONL by running sync commands that generate stream events and reconstruct state. This skill manages cross-format data flow to reduce friction and data drift across storage environments.

What is the best way to sync Claude Code task state to a shared log?

Syncing Claude Code task state to a shared log is done by running export commands to generate stream events, then using hydrate commands to reconstruct state. This lifecycle coordination keeps task streams consistent across environments.

How does hydrating task state from stream events work?

Hydrating task state from stream events reconstructs the full state from exported event logs. You run a sync export to generate the events, then the hydrate command rebuilds the complete task state from those serialized artifacts.

Can I use this to compact and migrate sync artifacts across environments?

Yes, you can compact and migrate sync artifacts across environments. The skill supports moving task state and related artifacts across storage formats, tools, and environments while applying compaction to streamline the serialized data.

Do I need specific dependencies to import and export tx task state?

No specific dependencies are required to import and export tx task state. The skill operates independently to manage data migration, hydrate state from events, and compact artifacts across SQLite, JSONL, and Claude Code directories.