database-migrations-migration-observability

Migration monitoring, CDC, and observability infrastructure

Quality

50%

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 ./skills/database-migrations-migration-observability/SKILL.md

Quality

Content

50%

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

The skill delivers substantial concrete code across CDC, monitoring, alerting, dashboards, and CI/CD, but it is monolithic with padded prose, non-executable snippets, and no validation-gated workflow. Every dimension sits at the mid anchor.

Suggestions

Make the examples executable: define 'this.migrations', resolve the undefined 'migration'/'event.source_db' references, and add the missing 'requests'/'prometheus' imports (or remove the unused 'np').

Collapse the duplicated Grafana dashboard configuration (sections 3 and 4) into one source and trim the 'You are a...' intro.

Add an explicit migration workflow with validation checkpoints (e.g. start monitoring -> run migration -> validate health/lag -> alert on failure), and consider moving the large code blocks into scripts/ references for progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly code but padded with a 'You are a database observability expert...' intro and duplicated dashboard configuration (sections 3 and 4), so it is 'mostly efficient but could be tightened'.	2 / 3
Actionability	Extensive concrete code is provided, but it is not executable as written: 'this.migrations' is never defined, 'migration' and 'event.source_db' are undefined, 'requests'/'prometheus' module references are unimported, and 'np' is imported but unused — 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	Content is organized as numbered topic examples rather than a sequenced workflow; the CI/CD block has a health-check step but no validate->fix->retry feedback loop, and missing validation for destructive/batch database operations caps this at 2.	2 / 3
Progressive Disclosure	No bundle files exist and all content (~410 lines) is inline in SKILL.md; sections provide some structure but content that could be split into reference files is not separated, matching 'some structure but could be better organized'.	2 / 3
	Total	8 / 12 Passed

Description

50%

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 clear niche but stays at noun-phrase level with no explicit 'when to use' trigger guidance and incomplete keyword coverage. All dimensions land at the mid anchor.

Suggestions

Add an explicit trigger clause, e.g. 'Use when monitoring database migrations, setting up CDC with Debezium/Kafka, or building migration alerting and dashboards.'

Replace noun phrases with concrete verbs/actions (e.g. 'Monitor migrations, configure CDC pipelines, instrument metrics, and automate alerting/dashboards').

Include natural keyword variations users would say: 'change data capture', 'Debezium', 'Kafka', 'replication lag', 'alerting'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Migration monitoring, CDC, and observability infrastructure') but only as noun phrases rather than listing concrete actions like 'monitor migrations, configure CDC pipelines, set up alerting', matching the 'names domain and some actions but not comprehensive' anchor.	2 / 3
Completeness	It states what the skill covers but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	'Migration monitoring', 'CDC', and 'observability' are relevant terms a user might say, but common variations such as 'change data capture', 'Debezium', 'Kafka', 'alerting', and 'dashboards' are absent, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The CDC-plus-migration-monitoring niche is reasonably distinct, but the broad 'observability infrastructure' phrase could overlap with other monitoring skills, matching 'somewhat specific but could still overlap'.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/database-migrations-migration-observability/SKILL.md
Commit: e63f7dd

Reviewed: about 3 hours 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.