database-migrations

Buenas prácticas de migración de base de datos para cambios de esquema, migraciones de datos, rollbacks y despliegues de tiempo cero en PostgreSQL, MySQL y ORMs comunes (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./docs/es/skills/database-migrations/SKILL.md

Quality

Content

72%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 highly actionable, well-organized migration reference with excellent code coverage, weakened only by a missing validate/retry feedback loop for destructive ops and a monolithic structure that should split per-ORM detail into reference files.

Suggestions

Add an explicit post-apply verification step with a feedback loop, e.g. run the migration in a staging copy, verify row counts/integrity, and rollback if checks fail.

Split each ORM section (Prisma, Drizzle, Kysely, Django, golang-migrate) into separate reference files and link to them from a concise overview in SKILL.md.

Trim redundant boilerplate across the per-tool workflow sections to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and dense — code, checklists, and an anti-pattern table with minimal explaining of concepts Claude already knows — though the ~430-line multi-tool breadth introduces some redundancy across ORM sections that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready bash commands, SQL, TypeScript and Python examples covering the common migration cases across all six tools.	5 / 5
Workflow Clarity	The expand-contract pattern and safety checklist give a clear sequence, but there is no explicit post-apply validate→fix→retry feedback loop; per guidelines, missing feedback loops for destructive/batch database operations caps this at 3.	3 / 5
Progressive Disclosure	Well-organized with per-tool section headers, but no bundle files exist and all per-ORM detail is inlined in one ~430-line SKILL.md; content that clearly belongs in separate reference files is not split out.	3 / 5
	Total	15 / 20 Passed

Description

66%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 specific, well-targeted description that names concrete migration actions and a broad toolset, but it lacks an explicit 'when to use' trigger clause that would push completeness higher.

Suggestions

Append an explicit trigger clause, e.g. 'Úsalo cuando el usuario mencione migraciones de base de datos, cambios de esquema, rollbacks o despliegues zero-downtime.'

Add a few natural synonyms users say ('migrate up/down', 'agregar/quitar columnas', 'sync schema') to broaden trigger coverage.

Optionally mention data backfill/seed explicitly to round out the action list.

Dimension	Reasoning	Score
Specificity	Lists several concrete action categories — 'cambios de esquema', 'migraciones de datos', 'rollbacks', 'despliegues de tiempo cero' — plus names specific databases and six ORMs, giving broad but not exhaustive coverage.	4 / 5
Completeness	The 'what' is clearly stated, but there is no explicit 'Use when...' / 'Usar cuando...' trigger clause; the 'when' is only weakly implied by the listed action categories, so per guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Strong natural keyword coverage ('migración de base de datos', 'rollbacks', 'despliegues de tiempo cero') plus tool names (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate), though a few common phrasings like 'migrate up/down' or 'schema sync' are absent.	4 / 5
Distinctiveness Conflict Risk	Clearly niched to database migrations with seven specific tools named, making it mostly distinct with only minor overlap risk against a generic SQL skill.	4 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: docs/es/skills/database-migrations/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.