litestream
This tool defines architecture and coding rules for handling SQLite WAL operations, LTX files, and storage backends in Litestream.
Install
mkdir -p .claude/skills/litestream && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9023" && unzip -o skill.zip -d .claude/skills/litestream && rm skill.zipInstalls to .claude/skills/litestream
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Expert knowledge for contributing to Litestream, a standalone disaster recovery tool for SQLite. Provides architectural understanding, code patterns, critical rules, and debugging procedures for WAL monitoring, LTX replication format, storage backend implementation, multi-level compaction, and SQLite page management. Use when working with Litestream source code, writing storage backends, debugging replication issues, implementing compaction logic, or handling SQLite WAL operations.Key capabilities
- →Monitor SQLite WAL
- →Convert changes to immutable LTX files
- →Replicate to cloud storage
- →Perform multi-level compaction
- →Manage SQLite page locks
How it works
The agent monitors the SQLite WAL, converts changes into immutable LTX files, and replicates them to cloud storage using a defined interface.
Inputs & outputs
When to use litestream
- →Debugging replication issues
- →Implementing storage backends
- →Contributing to Litestream source code
About litestream
Provides architecture details and coding rules for the Litestream project. It handles complex SQLite WAL operations, LTX file formats, and storage backend implementation.
Expert knowledge for contributing to Litestream, a standalone disaster recovery tool for SQLite. Provides architectural understanding, code patterns, critical rules, and debugging procedures for WAL monitoring, LTX replication format, storage backend implementation, multi-level compaction, and SQLite page management. Use when working with Litestream source code, writing storage backends, debugging replication issues, implementing compaction logic, or handling SQLite WAL operations.
When not to use it
- →Modifying existing LTX files
- →Writing directly to final storage paths
Prerequisites
Limitations
- →Single replica per database
- →Requires atomic file operations
How it compares
It provides expert architectural rules and invariants for disaster recovery that generic SQLite backup tools lack.
Compared to similar skills
litestream side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| litestream (this skill) | 0 | 9mo | Review | Advanced |
| run-tests | 1 | 8mo | Review | Intermediate |
| dbx-regenerate | 1 | 10mo | Review | Intermediate |
| advanced-lokstra-validate-consistency | 0 | 9mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
run-tests
pgschema
Run pgschema automated tests (go test) to validate diff logic, plan generation, and dump functionality using test fixtures
dbx-regenerate
storj
Regenerate DBX code after making changes to .dbx schema files. Runs code generation, shows diff summary, validates compilation, and reports any errors.
advanced-lokstra-validate-consistency
primadi
Validate application consistency - circular dependencies, schema validation, config checks, annotation validation, and service registration. Use after all code is implemented to identify issues before deployment.
passion-dev
awalvie
Passion climbing training app development. Use for: adding handlers, modifying DB models, creating templates, understanding project architecture, running/testing the app, YAML import features.
startup
matlockx
Use this skill for Go service bootstrapping with flachnetz/startup library. Covers options composition, auto-initialization, Postgres, Kafka, HTTP server, tracing, and environment patterns.
opentelemetry-instrumentation-extension
docker
Extend OpenTelemetry instrumentation when new functionality is added to the MCP Gateway. Use when (1) new operations/functions are added, (2) reviewing code for missing instrumentation, (3) user requests otel/telemetry additions, or (4) working with state-changing operations. Analyzes git diff, suggests instrumentation points following project standards in docs/telemetry/README.md, implements with approval, writes tests, updates documentation, and verifies with debug logging and docker logs.