Name: xata
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

xata

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

Quality

63%

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/xata/SKILL.md

Quality

Content

61%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 content is actionable and well-structured with strong executable CLI examples, but carries some unnecessary explanatory prose and—critically for a database integration—lacks validation/verification steps around action execution and proxy requests that could be destructive.

Suggestions

Add a verification/feedback-loop step after running actions and proxy requests (e.g. re-query to confirm a write, or check the response status/error field before proceeding), since Xata is a database where operations can be destructive.

Trim the marketing-style introduction and the filler "When to use which actions" line to respect the token budget.

Either show concrete action examples in the Popular actions section or move that detail into a reference file and link to it for progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-pasteable commands, but includes unnecessary prose such as the marketing-style intro ("Xata is a serverless data platform...") and the filler line "When to use which actions: Use action names and parameters as needed.", matching the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides concrete, executable commands for the common cases (install, login, connection ensure, action list/run, proxy with a full flag table), mostly copy-paste ready with only minor gaps like unresolved placeholders (CONNECTION_ID, QUERY) and the Popular actions section merely restating the discovery command.	4 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-feedback loop, but because Xata is a database and the action-run and proxy paths allow destructive operations (e.g. DELETE) with no validation or verification step, the rubric's destructive/batch cap limits this to 3.	3 / 5
Progressive Disclosure	With no bundle files present, the single ~140-line body is organized into clearly headed sections (Overview, Working with Xata, Authentication, Connecting, Searching, Popular actions, Proxy requests, Best practices) with good navigation, matching the good-structure anchor though content is all inline with no one-level-deep references.	4 / 5
	Total	14 / 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 correctly pairs a what-statement with an explicit Use-when trigger and leverages a distinctive product name, but its action verbs are generic and trigger-term coverage is narrow.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Create, query, and update records; search across tables; automate workflows".

Expand the trigger clause with natural variations users might say, e.g. "Use when the user wants to query, insert, or search Xata records, or automate Xata workflows."

Mention key Xata concepts (databases, branches, tables) in the description to strengthen specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Xata domain plus a few action categories, but the verbs ("manage", "automate") are generic rather than concrete, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It answers both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Xata data") with an explicit Use-when clause; the trigger could be more specific (e.g. mentioning records or workflows), so it sits above the clear-what/weak-when anchor but below the comprehensive-concrete-triggers anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Xata data" surfaces the natural keyword "Xata" that users would actually say, but coverage is limited to that single term with no synonyms or variations, matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"Xata" is a specific named product giving the skill a clear niche with distinct triggers and minimal conflict risk with other skills, matching the clear-niche anchor.	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/xata/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.