Install any skill in seconds. Free to start, no credit card required.
Get Started Free →opencti-platform/create-migration
Use when: creating a new ElasticSearch database migration file, adding or transforming data at deploy time
Passed 23 of 24 test cases with the skill, and 9 of 24 without it.
and 24 more in the full report
16 fixed8 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am writing a migration description for adding an enterprise setting field `enable_saml_sso`. What casing convention is required for the description part of the migration file name in OpenCTI? Should it be kebab-case (`enable-saml-sso`) or camelCase (`enableSamlSso`)?
| Checked | Without skill | With skill |
|---|---|---|
| The description in the migration file name uses snake_case. | Missed | Passed |
The instructions your model reads when the skill loads.
add_description_to_user).Use the current timestamp (ms) as prefix.
File: opencti-platform/opencti-graphql/src/migrations/<timestamp>-<description>.ts.
Use the standard template with logging and execution context.
import { logMigration } from '../config/conf';
const message = '[MIGRATION] <Description>';
export const up = async (next: (error?: Error) => void) => {
const startTime = Date.now();
logMigration.info(`${message} > started`);
// Implementation here
// usage: const context = executionContext('migration');
// await someDomainFunction(context, SYSTEM_USER, args);
logMigration.info(`${message} > done in ${Date.now() - startTime} ms`);
next();
};
export const down = async (next: (error?: Error) => void) => {
next();
};
test cases passed, vs 9 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.