database-migrations-migration-observability

Migration monitoring, CDC, and observability infrastructure

Quality

36%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/database-migrations-migration-observability/SKILL.md

The canonical home for this skill is database-migrations-migration-observability in rmyndharis/antigravity-skills

Quality

Content

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

The body provides rich, domain-relevant code but is verbose, not fully executable due to undefined references and missing imports, lacks a validated end-to-end migration workflow, and inlines material that should live in reference files.

Suggestions

Move the full CDC, enterprise-monitoring, dashboard, and CI/CD implementations into reference files (e.g. references/cdc.md, references/dashboards.md) and keep SKILL.md as a concise overview with one-level-deep links.

Fix the code so it is executable: set this.migrations in the constructor, import requests, use prometheus_client.CollectorRegistry consistently, and define or stub parse_cdc_event, apply_to_target, calculate_progress_stats, and handle_anomalies.

Add an explicit migration workflow with validation checkpoints (run migration → verify row counts/lag → on failure roll back or fix and re-run → only then proceed), especially given these are destructive batch operations.

Dimension	Reasoning	Score
Conciseness	Roughly 300 lines of full multi-class implementations are inlined in SKILL.md with duplicated metric/dashboard definitions, noticeably over-providing code Claude could derive from shorter hints.	2 / 5
Actionability	There is substantial concrete code, but it is not copy-paste ready: undefined references (this.migrations, migration, prometheus.CollectorRegistry), missing imports (requests), and undefined helpers (parse_cdc_event, apply_to_target, calculate_progress_stats) leave key gaps.	3 / 5
Workflow Clarity	The five numbered sections are topical recipes rather than a sequenced migration workflow, and destructive/batch migrations lack validate→fix→retry checkpoints; the only sequence is the CI/CD pipeline with a single health check.	2 / 5
Progressive Disclosure	No bundle files exist and the bulk implementations (CDC, dashboard, alerting, CI/CD) that clearly belong in separate reference files are inlined monolithically, with only section headers for structure.	2 / 5
	Total	9 / 20 Passed

Description

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

The description identifies a recognizable domain but lists topics rather than actions and omits any explicit trigger guidance, leaving both 'what' and 'when' underspecified. Trigger terms are relevant but thin on synonyms.

Suggestions

Rewrite the description in third person with concrete verbs, e.g. 'Monitors database migrations via CDC pipelines, collects Prometheus metrics, detects anomalies, and configures Grafana dashboards and alerts.'

Add an explicit 'Use when...' clause naming natural triggers such as 'database migration monitoring', 'CDC/Debezium pipelines', 'replication lag', or 'migration alerting'.

Include tool/synonym keywords (Debezium, Kafka, Prometheus, Grafana) so the description matches how users actually request this work.

Dimension	Reasoning	Score
Specificity	The phrase 'Migration monitoring, CDC, and observability infrastructure' names a concrete domain but contains no verbs or concrete actions — only noun phrases — so it sits below the midpoint toward the score-1 anchor.	2 / 5
Completeness	The 'what' is vague (a topic list with no actions) and there is no 'Use when...' trigger clause at all, matching the vague-what-and-no-when anchor rather than the clear-what anchor capped at 3.	2 / 5
Trigger Term Quality	'Migration monitoring', 'CDC', and 'observability' are relevant keywords a user might say, but common variations, synonyms, and tool names (Debezium, Kafka) are absent from the description.	3 / 5
Distinctiveness Conflict Risk	The CDC and migration-observability niche is mostly distinct with only minor overlap risk against closely related migration skills referenced in the body.	4 / 5
	Total	11 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/database-migrations-migration-observability/SKILL.md
Commit: 57c135b

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.