create-migration

Use when: creating a new ElasticSearch database migration file, adding or transforming data at deploy time

Quality

71%

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 ./.github/skills/create-migration/SKILL.md

Quality

Content

80%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 content is concise and well-structured with an executable template and concrete file-path rule, but a database-migration workflow that lacks any validation, dry-run, or rollback checkpoint caps its workflow clarity. Adding a verification step would meaningfully raise the score.

Suggestions

Add an explicit validation checkpoint after implementing the migration (e.g. run the migration against a test/staging index and verify expected document count or sample rows before considering it done).

Include guidance for verifying the down/rollback path actually reverses the change, since migrations are destructive and batch-oriented.

Replace the 'Implementation here' placeholder with a one-line concrete example of the executionContext + domain-function call pattern shown in the comment, so the template is closer to copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean (~35 lines) with no padding or explanation of concepts Claude already knows; the code template and path guidance each earn their place, matching the 'lean and efficient' anchor.	5 / 5
Actionability	Provides a concrete file path with a timestamp-prefix rule and a complete TypeScript up/down template with imports and logging, but the core migration logic is a placeholder ('Implementation here'), leaving a minor gap versus fully copy-paste-ready code.	4 / 5
Workflow Clarity	Steps are sequenced (generate file, implement pattern) but the skill performs a destructive/batch database migration with no validation, dry-run, or rollback-verification checkpoint, so workflow clarity is capped at 3 per the rubric.	3 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references (none of references/scripts/assets exist), and is organized into clear Prerequisites/Procedure/Step sections, satisfying the simple-skill exception for a 5.	5 / 5
	Total	17 / 20 Passed

Description

62%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 clearly states its niche and includes an explicit 'Use when' trigger, but its action list is narrow and trigger-term coverage lacks synonyms and file extensions. It is solid but not comprehensive.

Suggestions

Add concrete trigger phrases users would naturally say, such as 'ElasticSearch data migration', 'OpenCTI migration', or '.ts migration file', to broaden trigger-term coverage.

Expand the 'what' with one or two more specific actions (e.g. 'scaffold the up/down template with logging and execution context') to lift specificity toward comprehensive coverage.

Separate the 'what' and 'when' more explicitly so the 'when' reads as distinct trigger conditions rather than restating the actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('ElasticSearch database migration file') and two concrete actions ('creating a new ... migration file', 'adding or transforming data at deploy time'), matching the '1-2 concrete actions' anchor rather than the broader coverage of a 4.	3 / 5
Completeness	Both 'what' (creating migration files, adding/transforming data) and 'when' (explicit 'Use when:' clause) are answered, but the 'when' doubles as the 'what' and could be more specifically triggered, matching the 4 rather than the fully explicit 5.	4 / 5
Trigger Term Quality	Relevant keywords ('ElasticSearch', 'database migration', 'migration file', 'deploy time') are present but common variations and file extensions (e.g. '.ts', 'data migration') are missing, fitting the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	The ElasticSearch-database-migration niche is mostly distinct with clear triggers, but there is minor overlap risk with general migration or deploy-time data skills, placing it just below the 5 anchor.	4 / 5
	Total	14 / 20 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: OpenCTI-Platform/opencti
Path: .github/skills/create-migration/SKILL.md
Commit: cdafc20

Reviewed: 4 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.