Name: vitess
Rating: 90.3 (1 reviews)
Author: planetscale

vitess

Vitess best practices, query optimization, and connection troubleshooting for PlanetScale Vitess databases. Load when working with Vitess databases, sharding, VSchema configuration, keyspace management, or MySQL scaling issues.

1.16x

Quality

80%

Does it follow best practices?

Impact

93%

1.16x

Average score across 8 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/vitess/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 well-structured, token-efficient overview that points cleanly to a real reference bundle. Its weakness is actionability and workflow: the description promises query optimization and connection troubleshooting, but the body offers no executable examples or sequenced troubleshooting/validation steps for those tasks.

Suggestions

Add at least one concrete SQL/query-optimization example (e.g., rewriting a cross-shard scatter into a single-shard query by filtering on the vindex column) and a short connection-troubleshooting checklist, since both are promised in the description.

Provide a sequenced workflow with a validation checkpoint for destructive operations like Online DDL / deploy requests (e.g., validate schema on a branch, review deploy request, confirm no blocking warnings, then apply).

Move the 'Hosting' promotional blockquote and the 'recursive CTEs as of v21+' version note into tighter, less verbose phrasing (or a versioning/deprecated note) to recover conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly lean — bullet points, a concepts table, and a dense SQL-compatibility section that assume Claude's intelligence without explaining basics. The 'Hosting' blockquote is mildly verbose/promotional, and version-sensitive notes ('recursive CTEs as of v21+') sit outside a deprecated section, keeping it just below a 5.	4 / 5
Actionability	Some concrete actionable bits exist (ports 3306/443, SSL required, use Vitess Sequences for IDs, filter by vindex column, deploy requests for production changes), but the body is largely descriptive — no SQL examples for the promised 'query optimization' and no connection-troubleshooting steps, leaving guidance incomplete.	3 / 5
Workflow Clarity	The body is an organized overview but contains no multi-step workflow despite the description promising troubleshooting; destructive schema-change operations (Online DDL/deploy requests) are mentioned without validation/verification steps, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Clear overview body with a well-signaled references table mapping five real, one-level-deep reference files (all present in ./references/) to their use cases, with detail appropriately split out of the main file.	5 / 5
	Total	15 / 20 Passed

Description

95%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, third-person description that clearly states what the skill covers and gives an explicit 'Load when' trigger with concrete, natural keywords. It is comprehensive and distinct with negligible conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete action areas — 'query optimization, and connection troubleshooting' alongside 'best practices' — giving specific coverage with only minor gaps (e.g., no mention of schema/VSchema actions in the 'what' clause).	4 / 5
Completeness	Explicitly answers both what ('Vitess best practices, query optimization, and connection troubleshooting for PlanetScale Vitess databases') and when ('Load when working with Vitess databases, sharding, VSchema configuration, keyspace management, or MySQL scaling issues') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage with synonyms and variations — 'Vitess databases, sharding, VSchema configuration, keyspace management, or MySQL scaling issues' — these are phrases a user would naturally say when needing this skill.	5 / 5
Distinctiveness Conflict Risk	Clear Vitess/PlanetScale niche with distinct, domain-specific triggers that would not fire for unrelated database skills; minimal conflict risk.	5 / 5
	Total	19 / 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: planetscale/database-skills
Path: skills/vitess/SKILL.md
Commit: 73b20b7

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