turso

Turso and libSQL patterns for embedded SQLite-compatible databases, serverless drivers, sync engines, partial sync, WAL/MVCC behavior, compatibility gaps, CLI usage, and Drizzle integration boundaries. Use when mentioning Turso, libSQL, @libsql/client, remote SQLite, embedded replicas, or local database sync.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/turso/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-organized rule set that succeeds as a mental model but is weaker on actionability and workflow clarity, offering decision guidance rather than executable steps or explicit validation loops for risky sync/database operations.

Suggestions

Add at least one concrete code or CLI snippet (e.g. a libSQL client connect/embedded-replica example or a Turso CLI sync command) to lift actionability.

Add an explicit validate->fix->retry loop for sync and migration operations, e.g. after defining a partial-sync subset, run the integration tests covering sync lag and duplicate writes before proceeding.

Tighten bullets like "Document when data is local, when it syncs, and which writes are accepted" into a concrete checklist item rather than a generic instruction.

Dimension	Reasoning	Score
Conciseness	The body is a tight set of bullet rules that assume Claude's competence (e.g. "Treat Turso/libSQL as SQLite-compatible, not identical to every local SQLite deployment") with only minor phrasing that could be trimmed.	4 / 5
Actionability	Guidance is directional and decision-focused ("Decide whether the feature needs remote writes...", "define the subset boundary explicitly and test...") but lacks executable code, actual CLI commands, or concrete sync config examples.	3 / 5
Workflow Clarity	Sections give rough sequencing (Upstream Grounding describes an orient-then-verify flow) and some implicit checkpoints ("verify decisive details ... before changing code", "test that queries do not silently depend on unsynced rows"), but there is no explicit validate->fix->retry loop for the database/sync operations the rubric flags.	3 / 5
Progressive Disclosure	The body is under 50 lines with no bundle files and is organized into clear, well-labeled sections (Reference Repositories, Upstream Grounding, Driver Boundaries, Sync And Compatibility Checks, Operational Rules), matching the simple-skill exception for progressive disclosure.	5 / 5
	Total	15 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what/when structure and distinctive, natural trigger terms. Its main weakness is that it lists topic areas rather than concrete actions, keeping specificity at the midpoint.

Suggestions

Lead with concrete verbs (e.g. "Choose driver modes, define partial-sync boundaries, and verify SQLite compatibility for Turso/libSQL") instead of the generic "patterns for".

Add a couple of natural synonyms users might say, such as "edge database" or "distributed SQLite", to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description catalogs many concrete subject areas ("embedded SQLite-compatible databases, serverless drivers, sync engines, partial sync, WAL/MVCC behavior, compatibility gaps, CLI usage, and Drizzle integration boundaries"), but the only action verb is the generic "patterns for", so it names domain and specifics rather than concrete actions.	3 / 5
Completeness	It explicitly states what ("Turso and libSQL patterns for ...") and gives a concrete "Use when mentioning ..." trigger clause answering when, satisfying both halves with explicit trigger phrases.	5 / 5
Trigger Term Quality	The "Use when mentioning Turso, libSQL, @libsql/client, remote SQLite, embedded replicas, or local database sync" clause covers the natural terms users would say, though a few synonyms (e.g. "edge database", "distributed SQLite") are absent.	4 / 5
Distinctiveness Conflict Risk	Triggers like Turso, libSQL, @libsql/client, and embedded replicas are highly specific to a clear niche with minimal overlap against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: EpicenterHQ/epicenter
Path: .agents/skills/turso/SKILL.md
Commit: fe6d8de

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.