CtrlK
BlogDocsLog inGet started
Tessl Logo

convex-migration-helper

Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

Well-structured, actionable content with a clear multi-deploy workflow, explicit validation checkpoints, and clean progressive disclosure into two real reference files. The only slack is minor verbosity in the concept sections and migration-function code living in references rather than inline.

Suggestions

Tighten the "Schema Validation Drives the Workflow" section: the three bullets restate the single constraint above them and could be collapsed into one or two lines.

Consider including one minimal inline migration-function example (defineTableDataMigration with a dryRun snippet) so the most common case is copy-paste ready without opening references.

Trim "Online Migrations" / "Prefer New Fields Over Changing Types" to one line each; the current phrasing explains concepts Claude can largely infer.

DimensionReasoningScore

Conciseness

Mostly efficient with tight code and reference pointers, but the "Schema Validation Drives the Workflow" and adjacent concept sections restate constraints Claude could partly infer; minor trimming possible.

4 / 5

Actionability

Provides executable schema snippets, concrete npx commands, a numbered workflow, and a checklist; the actual migration-function code is deferred to references rather than inline, leaving minor gaps.

4 / 5

Workflow Clarity

The multi-deploy workflow is clearly sequenced with explicit validation checkpoints (dry run, verify migration complete) and a full checklist, satisfying the destructive/batch-operation feedback-loop requirement.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview with two well-signaled, one-level-deep references (migrations-component.md, migration-patterns.md) that both exist, with content appropriately split between overview and detail.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong, specific description that clearly states both capability and trigger conditions for a well-scoped niche. Minor keyword/synonym coverage is the only thing keeping specificity and trigger quality from a perfect score.

DimensionReasoningScore

Specificity

Names the domain plus the concrete methodology ("widen-migrate-narrow") and component ("@convex-dev/migrations"), listing several specific actions rather than 1-2; minor gaps keep it just below comprehensive.

4 / 5

Completeness

Explicitly answers both what ("Plans Convex schema and data migrations...") and when ("Use for breaking schema changes, backfills...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like "breaking schema changes", "backfills", "table reshaping", and "zero-downtime rollouts" match what a Convex user would say; a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The Convex-specific niche combined with migration-only triggers gives it a clear, distinct scope with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

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.

Repository
openclaw/clawhub
Reviewed

Table of Contents

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.