mysql-patterns

MySQL and MariaDB schema, query, indexing, transaction, replication, and connection-pool patterns for production backends. Use when designing MySQL or MariaDB schemas and indexes, or when a query, transaction, or replica lags.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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.

A high-quality, actionable MySQL/MariaDB reference with executable examples and explicit validation/rollback guidance for destructive operations. Minor redundancy and the absence of progressive-disclosure bundle files keep it just below full marks.

Dimension	Reasoning	Score
Conciseness	Lean code-first reference that assumes SQL competence and avoids basic concept padding, but the SKIP LOCKED caution is repeated three times and the upsert/version-check guidance overlaps slightly, so a few tokens could be trimmed.	4 / 5
Actionability	Copy-paste ready SQL, config, and driver code (SQLAlchemy, mysql2) covering upserts, keyset pagination, full-text, JSON, transactions, queue claims, and security with concrete, executable examples.	5 / 5
Workflow Clarity	The Output Expectations section gives a sequenced 5-step review workflow with an explicit validation plan (EXPLAIN, dry run, lock/deadlock check, rollback criteria) and the deadlock checklist provides a retry feedback loop; it is topic-organized rather than one linear flow, so not a full 5.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with inline examples appropriately placed for a reference skill and a Related section pointing to sibling skills, but no bundle reference files exist to offload the larger config/code blocks.	4 / 5
	Total	17 / 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.

A strong, specific, third-person description that explicitly states both capabilities and usage triggers scoped to MySQL/MariaDB. Minor gaps in trigger synonyms and action verb phrasing keep specificity and trigger quality at 4.

Dimension	Reasoning	Score
Specificity	Lists several specific capability areas ("schema, query, indexing, transaction, replication, and connection-pool patterns") for production backends, but these are domain nouns rather than concrete actions and omit security/migrations, so not a full 5.	4 / 5
Completeness	Explicitly answers both what (the pattern list) and when ("Use when designing MySQL or MariaDB schemas and indexes, or when a query, transaction, or replica lags") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms present ("MySQL", "MariaDB", "schemas", "indexes", "query", "transaction", "replica lags"), but a few common variations like "database", "DB", "slow query", and "deadlock" are missing.	4 / 5
Distinctiveness Conflict Risk	Niche is clearly scoped to MySQL/MariaDB with engine-specific triggers, minimizing overlap with the related postgres-patterns skill.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/mysql-patterns/SKILL.md
Commit: 06c5e11

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.