Migration Architect
PassAudited by ClawScan on May 1, 2026.
Overview
The skill appears to be a disclosed migration-planning toolkit, but users should carefully review its generated rollback and production-operation guidance before applying it.
This skill looks coherent for migration architecture work. Before installing or using it, confirm you are comfortable running the bundled Python scripts locally, and treat generated SQL, restore commands, and automatic rollback triggers as drafts that need review by database, SRE, and change-management owners before use in production.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The skill may ask the user or agent to run local Python helper scripts that read input JSON files and generate migration, compatibility, or rollback outputs.
The skill documents running bundled Python scripts locally and writing output files. This is disclosed and central to the migration-planning purpose, but users should understand that installing the skill involves local code execution even though no install spec or required binary is declared.
python3 scripts/migration_planner.py --input assets/sample_database_migration.json --output migration_plan.json --format both
Run the scripts only from the reviewed skill package, with intended input files, and review generated outputs before applying them to real systems.
If a generated runbook is applied directly, it could trigger production rollback actions, restore a database, or remove migration artifacts.
The sample rollback runbook includes automatic rollback triggers and production database recovery or cleanup commands. These are purpose-aligned for rollback planning, but they are high-impact if copied into automation or executed without approval.
Auto-Execute: Yes ... Recovery Scripts: pg_restore -d production -c /backups/pre_migration_backup.sql ... DROP TABLE IF EXISTS migration_log;
Require human approval, staging validation, backups, and change-management controls before using generated rollback scripts or enabling any automatic rollback action.