migrate-from-v1
Finish migrating a NanoClaw v1 install into v2. Run after `bash migrate-v2.sh` completes. Seeds the owner, migrates legacy memory, reconciles container configs, and helps port custom v1 code. Triggers on "migrate from v1", "finish migration", "v1 migration".
Profile →npx skills add nanocoai/nanoclaw --skill migrate-from-v1 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Finish v1 → v2 migration `bash migrate-v2.sh` already ran the deterministic migration. It handled: - .env keys merged - v2 DB seeded (agent_groups, messaging_groups, wiring) - Group folders copied (v1 CLAUDE.md → v2 CLAUDE.local.md) - Session data copied with conversation continuity (incl. Claude Code memory + JSONL transcripts) - Scheduled tasks ported - Channel code installed and auth state copied (incl. WhatsApp Baileys keystore) - WhatsApp LIDs resolved from `store/auth` and aliased into `messaging_groups` - Container skills copied - Container image built Your job is the parts that need human judgment: triage failed steps, seed the owner, run the shared-memory migration, reconcile configs, and port fork customizations. Read `logs/setup-migration/handoff.json` first — it has `overall_status`, per-step results in `steps`, and a `followups` list. ## Preflight: was the script run? Before anything else, check that `logs/setup-migration/handoff.json` exists. If it doesn't, the user is invoking this skill before `migrate-v2.sh` ran. Stop and tell them, verbatim: > This skill finishes a migration that `migrate-v2.sh` started. Run that first, in your terminal — not from inside Claude:
- Preflight: was the script run?
- Phase 0: Get v2 routing real messages
- 0a — Fix blockers only
- 0b — Smoke test, then continue
- Deferred failures
- Phase 1: Owner and access
- Access policy
- Phase 2: Migrate legacy memory
- Phase 3: Container config
- Phase 4: Fork customizations
- Principles
- Setup steps you can run
- When done
bash migrate-v2.sh cd <v1_path> git remote -v git log --oneline <upstream>/main..HEAD 2>/dev/null pnpm exec tsx setup/index.ts --step <name> pnpm exec tsx setup/index.ts --step verify systemctl --user restart "$UNIT" launchctl kickstart -k "gui/$(id -u)/$LABEL"
What does the migrate-from-v1 skill do?
Finish migrating a NanoClaw v1 install into v2. Run after `bash migrate-v2.sh` completes. Seeds the owner, migrates legacy memory, reconciles container configs, and helps port custom v1 code. Triggers on "migrate from v1", "finish migration", "v1 migration".
How do I install it?
Run `npx skills add nanocoai/nanoclaw --skill migrate-from-v1 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nanocoai/nanoclaw, a repository with 30,426 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.