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.

93

1.14x
Quality

92%

Does it follow best practices?

Impact

93%

1.14x

Average score across 8 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

This is a well-structured, concise MySQL skill that effectively serves as a decision-making guide and overview document. Its main strength is the excellent progressive disclosure pattern with lean inline guidance pointing to detailed references. The primary weakness is the lack of executable code examples — no SQL snippets for EXPLAIN analysis, no example DDL statements, no sample queries demonstrating the recommended patterns — which limits immediate actionability.

Suggestions

Add 1-2 executable SQL examples in key sections, such as a sample EXPLAIN output interpretation in Query Optimization or a sample CREATE TABLE statement in Schema Design demonstrating the recommended PK pattern.

Include a concrete example of cursor-based pagination vs OFFSET pagination to make that recommendation immediately actionable.

DimensionReasoningScore

Conciseness

The content is lean and efficient throughout. Every bullet point delivers actionable, non-obvious guidance specific to MySQL/InnoDB. It avoids explaining what MySQL is or how databases work, and trusts Claude's existing knowledge while adding domain-specific best practices.

3 / 3

Actionability

The guidance is concrete and specific (e.g., 'BIGINT UNSIGNED AUTO_INCREMENT', 'batch inserts 500-5000 rows', 'error 1213 with backoff'), but lacks executable code examples or copy-paste ready SQL/commands. The skill relies heavily on terse bullet points and external references rather than providing inline executable snippets.

2 / 3

Workflow Clarity

The top-level workflow is clearly sequenced with 5 explicit steps including validation ('EXPLAIN', 'EXPLAIN ANALYZE', lock/connection metrics) and production safety (rollback and post-deploy verification). The guardrails section adds explicit human approval requirements for destructive operations, completing the feedback loop.

3 / 3

Progressive Disclosure

The skill is excellently structured as a concise overview with well-organized sections, each containing brief inline guidance plus clearly signaled one-level-deep references to detailed markdown files. Navigation is intuitive with topical grouping (Schema, Indexing, Partitioning, etc.).

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that covers specific capabilities, includes natural trigger terms, explicitly states both what the skill does and when to use it, and is clearly scoped to MySQL/InnoDB. It follows third-person voice throughout and avoids vague language or buzzwords. The description is concise yet comprehensive.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: schema planning/review, indexing, query tuning, transactions, operations, diagnosing slow/locking behavior, planning migrations, troubleshooting replication and connection issues.

3 / 3

Completeness

Clearly answers both 'what' (plan and review schema, indexing, query tuning, transactions, operations) and 'when' with explicit triggers ('Use when creating or modifying MySQL tables, indexes, or queries; diagnosing slow/locking behavior; planning migrations; or troubleshooting replication and connection issues').

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: MySQL, InnoDB, tables, indexes, queries, slow, locking, migrations, replication, connection issues. These are all terms a user would naturally use when seeking MySQL help.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to MySQL/InnoDB specifically, which distinguishes it from general database skills or PostgreSQL-specific skills. The trigger terms are MySQL-specific (InnoDB, replication) reducing conflict risk with other database skills.

3 / 3

Total

12

/

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.

Validation11 / 11 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.