CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

90

1.16x
Quality

81%

Does it follow best practices?

Impact

93%

1.16x

Average score across 8 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-organized, token-efficient reference overview that defers detail cleanly to existing reference files with excellent navigation. The main gap is that the body offers specific recommendations but no executable examples or worked snippets, and there is no multi-step workflow with validation checkpoints.

Suggestions

Add one short copy-paste-ready example per high-value topic in the body (e.g., a minimal VSchema snippet with a hash vindex, or a sample deploy-request command) to lift actionability.

For destructive/batch operations mentioned (Online DDL, schema changes, resharding), add a brief validate-before-proceed checkpoint sequence so workflow clarity reflects a real procedure rather than only conceptual sections.

DimensionReasoningScore

Conciseness

Lean and efficient body with no padding of concepts Claude already knows; the one-line intro, compact capabilities bullets, and key-concepts table each earn their place, and the SQL-compatibility section surfaces non-obvious Vitess-specific limitations.

3 / 3

Actionability

Provides concrete specific guidance (ports 3306/443, SSL required, "use deploy requests for production changes", "Use Vitess Sequences... or app-generated IDs", "Rewrite as joins") but no executable code/commands or worked examples in the body; the copy-paste-ready depth is deferred to the reference files.

2 / 3

Workflow Clarity

Content is well organized into logical sections (capabilities, key concepts, PlanetScale specifics, SQL compatibility, references), but there is no multi-step process or validation checkpoint sequence — appropriate for a reference skill but not a sequenced procedure.

2 / 3

Progressive Disclosure

Clear concise overview with a well-signaled one-level-deep References table (topic + link + "Use for" column) pointing to 5 real reference files that all exist in ./references/, giving easy navigation without nested indirection.

3 / 3

Total

10

/

12

Passed

Description

90%

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, well-structured description that clearly states both what the skill covers and when to load it, with distinctive natural trigger terms. The only weakness is the mild vague-fluff lead phrase "best practices" framing capabilities as topics rather than crisp actions.

Suggestions

Replace the vague opener "Vitess best practices" with concrete verbs/actions (e.g., "Optimize queries, troubleshoot connections, and configure VSchema/sharding for PlanetScale Vitess databases").

DimensionReasoningScore

Specificity

Names the domain and several specific areas ("query optimization, and connection troubleshooting", "sharding", "VSchema configuration", "keyspace management", "MySQL scaling"), but the lead phrase "Vitess best practices" is vague fluff and the capabilities read as a topic catalog rather than crisp concrete actions like "extract/fill/merge".

2 / 3

Completeness

Explicitly answers both what ("Vitess best practices, query optimization, and connection troubleshooting for PlanetScale Vitess databases") and when via an explicit "Load when..." trigger clause.

3 / 3

Trigger Term Quality

Strong coverage of natural terms a user would actually say — "Vitess databases", "sharding", "VSchema configuration", "keyspace management", "MySQL scaling issues" — matching the rubric's good coverage anchor.

3 / 3

Distinctiveness Conflict Risk

Highly specific Vitess/PlanetScale niche with distinctive terms (Vitess, VSchema, keyspace, sharding) unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
planetscale/database-skills
Reviewed

Table of Contents

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.