Copy the legacy bun:sqlite smithers.db into PGlite or Postgres and write the migrated.json marker. Run `smithers migrate --help` for usage details.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add smithersai/smithers --skill smithers-migrate --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Smithers Migrate?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/smithersai-smithers-migrate)More formats (shields.io, HTML) on the badges page.
---
name: smithers-migrate
description: Copy the legacy bun:sqlite smithers.db into PGlite or Postgres and write the migrated.json marker. Run `smithers migrate --help` for usage details.
requires_bin: smithers
command: smithers migrate
---
# smithers migrate
Copy the legacy bun:sqlite smithers.db into PGlite or Postgres and write the migrated.json marker.
## Options
| 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 |
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
