What problem does it solve? After running the deterministic migrate-v2.sh script, a NanoClaw v1-to-v2 migration still has judgment-dependent leftovers: unseeded owner roles, bloated CLAUDE.local.md files full of obsolete v1 boilerplate, unverified container mounts, and fork customizations that need triage. This Skill guides an AI agent through finishing those steps safely. ## Core Features & Use Cases - Migration handoff triage: Reads logs/setup-migration/handoff.json, fixes blocking failures, and smoke-tests that v2 routes real messages before deeper work. - Owner and access setup: Grants the owner role via the permissions DB helpers and configures unknown_sender_policy (public, strict, or request_approval), optionally importing known senders from the v1 message database. - CLAUDE.local.md cleanup: Diffs each group's file against its v1 template, strips stock boilerplate now handled by v2 fragments, fixes stale workspace paths, and shows proposed content before writing. - Container config and fork porting: Validates additionalMounts host paths, converts fallback sidecar configs, and helps copy or archive v1 fork customizations. - Use Case: You ran bash migrate-v2.sh and the bot is up, but your agent groups still carry v1 instructions and nobody has admin rights. Invoke this Skill to finish the migration end to end. ## Quick Start Ask the agent to finish the v1 migration by saying "finish my NanoClaw v1 to v2 migration" after migrate-v2.sh has completed.