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
92%
Does it follow best practices?
Impact
93%
1.14xAverage score across 8 eval scenarios
Advisory
Suggest reviewing before use
Quality
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 follows best practices. It uses third person voice, provides specific concrete actions, includes comprehensive trigger terms that users would naturally use, and has an explicit 'Use when' clause covering multiple scenarios. The MySQL/InnoDB focus makes it clearly distinguishable from other database-related skills.
| 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...diagnosing slow/locking behavior...planning migrations...troubleshooting replication'). Includes explicit 'Use when' clause with comprehensive triggers. | 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 general database skills or other DBMS-specific skills. The mention of MySQL-specific concepts like InnoDB, replication, and connection issues 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, highly efficient skill that serves as an excellent overview document. It excels at conciseness and progressive disclosure, providing clear navigation to detailed references. The main weakness is the lack of executable SQL examples in the main document—guidance is specific but not copy-paste ready.
Suggestions
Add 1-2 executable SQL examples for common operations (e.g., a sample EXPLAIN analysis, a cursor pagination query pattern) to improve actionability
Include a concrete example of the validation step showing actual EXPLAIN output interpretation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every bullet point delivers actionable guidance without explaining basic concepts. No padding or unnecessary context—assumes Claude understands MySQL fundamentals. | 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. References external files for details rather than including copy-paste ready SQL. | 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 constraints for destructive operations. | 3 / 3 |
Progressive Disclosure | Excellent structure with concise overview sections and well-organized one-level-deep references. Each topic area links to specific reference files with clear naming. Easy to navigate and find detailed information. | 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.
b156f4c
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.