Individual skill

sqlite-turso

Use when deciding whether plain SQLite is enough, or wiring SQLite, Turso or libSQL for local-first, edge and embedded-replica apps — a local file DB, a remote Turso URL, or a local replica synced to a remote primary — plus WAL mode and SQLite's single-writer model and its lock errors. NOT Drizzle schema or queries on libSQL (that is `drizzle-orm`), NOT versioned up/down migrations (that is `db-migrations`), NOT serverless Postgres with branching (that is `neon`).

skills/sqlite-turso/SKILL.md

Read pinned source

Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
561
Repository last updated
Nov 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# SQLite & Turso/libSQL — decide, connect, operate

SQLite is an in-process, single-file, **single-writer** relational engine. Turso/libSQL is the
fork that adds a remote edge database and — the part people actually want — **embedded replicas**:
a local SQLite file that syncs to a remote primary, so reads are microsecond-local and writes still
land durably in the cloud.

This skill is **decide + connect + operate**. It owns the engine truths (WAL, single writer,
pragmas), the three deployment shapes, and wiring the current `@libsql/client`. It does NOT own
schema modeling or type-safe queries (that is `drizzle-orm`), versioned migration files (that is
`db-migrations`), or backup strategy as a primary task (that is `backups`).

## Is SQLite/Turso the right tool?