Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →smithersai/smithers-migrate
Copy the legacy bun:sqlite smithers.db into PGlite or Postgres and write the migrated.json marker. Run `smithers migrate --help` for usage details.
Passed 21 of 21 test cases with the skill, and 4 of 21 without it.
and 19 more in the full report
18 fixed4 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
What data type is expected for the --keepSqlite flag in the store migration CLI, and what is its default value?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies --keepSqlite as a boolean defaulting to true | Missed | Passed |
The instructions your model reads when the skill loads.
Copy the legacy bun:sqlite smithers.db into PGlite or Postgres and write the migrated.json marker.
| Flag | Type | Default | Description |
|---|---|---|---|
--from | string | Source backend; inferred when exactly one store has runs | |
--to | string | Target backend; required (pglite, postgres, or sqlite) | |
--url | string | Postgres connection URL when --to postgres | |
--keepSqlite | boolean | true | Keep the legacy SQLite database after a successful copy |
--agent | boolean | false | Run the durable migrate-repair workflow instead of deterministic migration |
test cases passed, vs 4 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.