mysql-patterns

MySQL and MariaDB schema, query, indexing, transaction, replication, and connection-pool patterns for production backends.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

92%

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

Highly actionable and concise reference with strong validation feedback loops; the main gap is progressive disclosure — all content lives inline in a single large file with no references to split material out.

Suggestions

Move the longer worked examples (Connection Pools, Configuration) into reference files under references/ and link to them from SKILL.md to reduce the inline footprint.

Add a brief "Quick reference" or "When to use each section" index near the top so the large body is easier to navigate.

Dimension	Reasoning	Score
Conciseness	Lean, dense reference material that assumes Claude's competence — no boilerplate explaining what MySQL or a connection pool is, and tables/prose each earn their place.	3 / 3
Actionability	Provides executable SQL, runnable SQLAlchemy/mysql2 pool configs, and specific diagnostic commands that are copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	Includes a deadlock/lock-wait checklist with a bounded retry loop and an Output Expectations validation plan (EXPLAIN, migration dry run, lock/deadlock check, rollback criteria) for destructive/batch database operations.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a monolithic ~400-line SKILL.md with no bundle references; content such as full pool/config examples could be split into one-level-deep reference files.	2 / 3
	Total	11 / 12 Passed

Description

82%

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 specific, well-scoped description with strong trigger terms and low conflict risk, but it lacks an explicit "Use when..." trigger clause so completeness is capped at 2.

Suggestions

Append an explicit trigger clause, e.g. "Use when designing or reviewing MySQL/MariaDB schema, migrations, slow queries, transactions, replication, or connection pools."

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas — "schema, query, indexing, transaction, replication, and connection-pool patterns" — rather than vague language, matching the multi-action anchor.	3 / 3
Completeness	Clearly states what the skill covers but has no "Use when..." clause or explicit trigger guidance, so the "when" is only implied — capped at 2 per the judging guideline.	2 / 3
Trigger Term Quality	Includes natural terms users actually say — "MySQL", "MariaDB", "schema", "indexing", "transaction", "replication", "connection-pool" — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped explicitly to MySQL and MariaDB production backends, a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: 754b8dd

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.