CtrlK
BlogDocsLog inGet started
Tessl Logo

mysql

Plan and review MySQL/InnoDB schema, indexing, query tuning, transactions, and operations. Use when creating or modifying MySQL tables, indexes, or queries; diagnosing slow/locking behavior; planning migrations; or troubleshooting replication and connection issues. Load when using a MySQL database.

92

1.14x
Quality

90%

Does it follow best practices?

Impact

93%

1.14x

Average score across 8 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 is a well-organized, token-efficient overview that delegates detail to verified reference files and provides a validated, rollback-aware workflow with concrete actionable heuristics. It is an exemplar of progressive disclosure for a database operations skill.

DimensionReasoningScore

Conciseness

Lean bullet-style guidance throughout that assumes Claude's competence and avoids explaining basics Claude already knows; every token earns its place.

5 / 5

Actionability

Highly specific, executable directives with concrete thresholds and identifiers ('Batch inserts (500–5000 rows)', 'Retry error 1213 with backoff', 'drop indexes with count_read = 0'), but as an instruction-style skill it lacks copy-paste code examples for the common cases.

4 / 5

Workflow Clarity

Clear five-step workflow with explicit validation ('Validate with evidence (EXPLAIN, EXPLAIN ANALYZE, lock/connection metrics)'), rollback, post-deploy verification, and a guardrail requiring human approval before destructive operations.

5 / 5

Progressive Disclosure

Topical overview with each section pointing to clearly signaled one-level-deep references; all 18 referenced files exist in references/ and navigation is straightforward with no nested references.

5 / 5

Total

19

/

20

Passed

Description

87%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 is clear, third-person, and explicitly states both capabilities and trigger conditions with strong natural phrasing. It is comprehensive in what/when coverage and well-distinguished from other skills.

DimensionReasoningScore

Specificity

Names the domain and five concrete capability areas ('schema, indexing, query tuning, transactions, and operations') but lists categories rather than fully granular actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Plan and review MySQL/InnoDB schema, indexing, query tuning, transactions, and operations') and when ('Use when creating or modifying MySQL tables... Load when using a MySQL database') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger phrases ('creating or modifying MySQL tables, indexes, or queries', 'diagnosing slow/locking behavior', 'planning migrations', 'troubleshooting replication and connection issues') with a few synonyms/extensions missing.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to the MySQL/InnoDB niche with distinct triggers, presenting minimal conflict risk with other skills.

5 / 5

Total

18

/

20

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.

Validation — 16 / 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.