CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/migration-operation-taxonomy

Classifies every DDL and DML statement in a database migration into an eight-category operation taxonomy (additive, backwards-compatible alter, locking, lock-escalating, breaking, data-loss, unsafe default, index-missing foreign key) and assigns a Critical, Warning, or Info severity justified by the lock mode and table-rewrite behavior the target engine actually performs. Records where PostgreSQL and MySQL/InnoDB diverge for the same logical statement, and where behavior is version-gated (PostgreSQL 11 removed the table rewrite for a constant DEFAULT; MySQL 8.0.12 made ADD COLUMN instant). Use when a migration file appears in a diff or a review queue and someone must decide, before it reaches a production-sized table, which statements are safe and which will stall writes or destroy data.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A precise, evidence-based classification skill with a clear sequenced workflow, strong validation checkpoints, and a well-signaled one-level-deep reference. The only weakness is conciseness: verbatim doc quotes could be trimmed to their load-bearing fragments.

Suggestions

Trim verbatim documentation quotes to the load-bearing clause (e.g. reduce 'Other transactions can still read the table, but if they try to insert, update, or delete rows in the table they will block until the index build is finished' to 'a SHARE lock blocks inserts/updates/deletes until the build finishes') to reclaim tokens.

The four-step procedure is the spine; consider a one-line recap at the top ('split → categorize → hazard-check → emit one row per statement + count block') so the reader has the pipeline before the dense per-check detail.

DimensionReasoningScore

Conciseness

High-signal niche content (engine lock modes, version gates, FK lock behavior) that assumes Claude's competence and avoids explaining basics, but the body leans verbose: long verbatim quotes from the PostgreSQL/MySQL docs ('Other transactions can still read the table, but if they try to insert, update, or delete rows ...') could be tightened to the load-bearing fragment without losing the claim.

2 / 3

Actionability

Concrete and executable throughout: an eight-category table with default severities, five named engine hazard checks each yielding a verdict, a required output shape with example rows and a count block, plus an explicit anti-patterns list — Claude knows exactly what to produce.

3 / 3

Workflow Clarity

Clearly sequenced (Step 1 inputs → Step 2 split → Step 3 categorize → Step 4 hazard checks → output) with explicit validation checkpoints for a destructive/batch domain: 'say unknown rather than guessing', size 'unverified', unknown engine → 'classify ... in every engine you plausibly target', version-gated severities 'reported as a range, not a value'.

3 / 3

Progressive Disclosure

SKILL.md is the overview/procedure; the consolidated engine tables and worked example are offloaded one level deep to references/engine-quick-reference.md, which exists and is clearly signaled ('are in references/engine-quick-reference.md'). Sections are well-organized and easy to navigate.

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.

A strong, third-person description that names concrete capabilities, an explicit 'Use when' trigger, and a distinct niche with engine/version specifics. No fluff or over-claims; every clause earns its place.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Classifies every DDL and DML statement ... into an eight-category operation taxonomy', 'assigns a Critical, Warning, or Info severity justified by the lock mode and table-rewrite behavior', 'Records where PostgreSQL and MySQL/InnoDB diverge' — each tied to specific engine/version facts.

3 / 3

Completeness

Explicitly answers both what (classify statements, assign severity, record divergences/version-gates) and when via an explicit 'Use when a migration file appears in a diff or a review queue ...' trigger clause.

3 / 3

Trigger Term Quality

Uses natural terms a reviewer would say — 'migration file', 'diff', 'review queue', 'DDL and DML', 'production-sized table' — with good coverage of the phrasings that would surface this skill.

3 / 3

Distinctiveness Conflict Risk

A clear niche (database migration operation taxonomy + severity classification) with distinct triggers; unlikely to fire for unrelated 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents