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.
Overall
score
93%
Does it follow best practices?
Evaluation — 94%
↑ 1.04xAgent success when using this skill
Validation for skill structure
Discovery
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 an excellent skill description that hits all the marks. It uses third person voice, lists specific concrete capabilities, includes comprehensive natural trigger terms, explicitly states both what the skill does and when to use it, and is clearly distinguishable from other database-related skills through MySQL/InnoDB-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'schema, indexing, query tuning, transactions, and operations' plus specific scenarios like 'creating or modifying MySQL tables, indexes, or queries; diagnosing slow/locking behavior; planning migrations; troubleshooting replication and connection issues.' | 3 / 3 |
Completeness | Clearly answers both what ('Plan and review MySQL/InnoDB schema, indexing, query tuning, transactions, and operations') AND when ('Use when creating or modifying MySQL tables...') with explicit trigger guidance including a 'Load when' clause. | 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 terms users naturally use when seeking database help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to MySQL/InnoDB with distinct triggers that wouldn't overlap with PostgreSQL, MongoDB, or general database skills. The explicit mention of MySQL-specific features like InnoDB and replication creates a clear niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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, token-efficient skill that provides clear workflow guidance and excellent progressive disclosure through organized reference links. The main weakness is the lack of executable code examples - the guidance is specific but not copy-paste ready, relying on bullet-point recommendations rather than concrete SQL snippets.
Suggestions
Add 1-2 executable SQL examples for common operations (e.g., a sample EXPLAIN analysis, a cursor pagination query pattern, or an online DDL statement)
Include a concrete example of the validation step showing actual EXPLAIN output interpretation or lock metric queries
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line provides actionable guidance without explaining concepts Claude already knows. No padding or unnecessary context about what MySQL is or how databases work. | 3 / 3 |
Actionability | Provides specific guidance (e.g., 'BIGINT UNSIGNED AUTO_INCREMENT', 'utf8mb4_0900_ai_ci', batch sizes '500-5000 rows') but lacks executable code examples. Recommendations are concrete but not copy-paste ready SQL/commands. | 2 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit validation checkpoint (step 4: EXPLAIN, metrics) and rollback/verification requirements for production changes. Guardrails section adds safety for destructive operations. | 3 / 3 |
Progressive Disclosure | Excellent structure with concise overview sections and well-signaled one-level-deep references to detailed materials. Each topic area links to specific reference files without nesting. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Table of Contents
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.