Name: turso
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

turso

Turso integration. Manage data, records, and automate workflows. Use when the user wants to interact with Turso data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

67%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.

The body delivers strong, executable CLI guidance with a clear connection workflow and validation feedback loops. Weaknesses are mild verbosity in introductory prose, placeholder-heavy commands without a fully worked example, and minor workflow-numbering inconsistencies.

Suggestions

Trim introductory padding (the Turso definition paragraph, "so you can focus on integration logic rather than auth plumbing", "This is the fastest way to get a connection") to assume Claude's competence.

Add one fully-worked end-to-end example with real values, e.g. a concrete action id and the resulting output field, so the run-action flow is copy-paste ready.

Fix the workflow numbering: label the main connect step "1a" to match the existing "1b", and add an explicit "Step 2" header that the "skip to Step 2" reference points to.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes trimmable explanation such as the "Turso is an open-source, distributed SQLite database platform" intro, "so you can focus on the integration logic rather than auth plumbing", and "This is the fastest way to get a connection", fitting anchor 3 rather than the minor-only over-explanation of a 4.	3 / 5
Actionability	It provides many concrete, executable commands (install, login, connection ensure, action list/run, request proxy with a flags table), but several are placeholder-heavy (CONNECTION_ID, actionId, QUERY, <id>) and there is no fully-worked end-to-end example with real values, matching anchor 4 with minor gaps.	4 / 5
Workflow Clarity	The connect-poll-search-run-proxy sequence is clear with validation checkpoints and a feedback loop (state checks, CLIENT_ACTION_REQUIRED re-poll, error-field handling), but it references an unlabeled "Step 2" and a "1b" with no "1a", a minor structural gap that keeps it below 5.	4 / 5
Progressive Disclosure	The content is well organized into clear sections with easy navigation and no nesting, but it is a single ~140-line file with no separate reference files or signaled one-level-deep references, fitting anchor 4 rather than the split-content ideal of a 5.	4 / 5
	Total	15 / 20 Passed

Description

66%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.

The description cleanly states what the skill does and when to use it with an explicit Use-when clause tied to a distinctive brand trigger. Its main weakness is generic action verbs and missing natural synonyms (database, SQLite, libSQL) that would improve trigger coverage.

Suggestions

Replace generic verbs with concrete Turso actions, e.g. "Manage Turso databases, schemas, tables, and rows, and automate workflows with Turso data."

Add natural synonyms and trigger phrases users actually say, such as "database", "SQLite", "libSQL", or "edge database".

Expand the "when" clause with concrete triggers, e.g. "Use when the user wants to query or manage Turso databases, tables, or records."

Dimension	Reasoning	Score
Specificity	The description names the Turso domain plus a few actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete Turso operations, fitting anchor 3 and falling short of the several specific actions needed for a 4.	3 / 5
Completeness	It provides both a "what" (manage data, records, automate workflows) and an explicit "when" clause ("Use when the user wants to interact with Turso data"), but the single trigger phrase is less concrete and comprehensive than the anchor-5 example.	4 / 5
Trigger Term Quality	It includes relevant keywords ("Turso", "data", "records", "interact with Turso data") but omits common natural synonyms a user might say such as "database", "SQLite", "libSQL", or "query", matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	"Turso" is a distinct product brand giving the skill a clear niche with minimal conflict risk, matching anchor 5 despite some generic secondary phrasing.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/turso/SKILL.md
Commit: f484c82

Reviewed: 3 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.