skills.rest
chiptoe-svg
chiptoe-svgCOMMUNITY
Explore all skills by this author →
GitHub

migrate-from-v1

Complete post-script NanoClaw v1 to v2 migration steps with validation checkpoints.

5|Updated Mar 14, 2026
Search Tags:#migration#configuration#cleanup#classroom#nanoclaw#porting#v1-to-v2
One-click install
npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill migrate-from-v1-chiptoe-svg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-from-v1
Source: https://github.com/chiptoe-svg/nanoclaw_gccourse/tree/main/.claude/skills/migrate-from-v1
Command: npx skills add https://github.com/chiptoe-svg/nanoclaw_gccourse --skill migrate-from-v1-chiptoe-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running the initial migrate-v2.sh script only handles deterministic migration steps, leaving critical manual tasks like triaging failed steps, seeding the owner user, cleaning up legacy v1 configuration files, reconciling container settings, and porting custom v1 code that are error-prone to complete manually.

Core Features & Use Cases

  • Failed Step Triage: Identifies and resolves migration failures that block the v2 router from handling messages.
  • Owner & Access Setup: Seeds the owner user role and configures sender access policies for the new v2 instance.
  • Legacy Config Cleanup: Removes v1 boilerplate from CLAUDE.local.md files while preserving user customizations, and updates path references to match v2 structure.
  • Custom Code Porting: Safely ports portable v1 customizations like skills and docs to the v2 codebase, with non-portable source code stashed for reference.
  • Use Case: An instructor upgrading their NanoClaw classroom instance from v1 to v2 can use this skill to complete the full migration without manual configuration errors, ensuring all their custom agent personas and skills carry over correctly.

Quick Start

Use the migrate-from-v1 skill to finalize your NanoClaw v1 to v2 migration after running the initial migrate-v2.sh script in your terminal.

Frequently Asked Questions about migrate-from-v1

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I finish NanoClaw v1 to v2 migration after running the initial script?▼

NanoClaw v1 to v2 migration is finalized by triaging failed script steps, seeding the owner user role, cleaning legacy v1 configuration files, reconciling container config, and porting custom v1 code to the new v2 codebase.

What manual configuration steps are needed for NanoClaw v2 porting?▼

NanoClaw v2 porting requires seeding the owner user role, configuring sender access policies, removing v1 boilerplate from CLAUDE.local.md while preserving customizations, and updating path references to match the v2 directory structure.

Can I safely port custom skills and docs during classroom NanoClaw migration without data loss?▼

Classroom NanoClaw migration safely ports portable v1 customizations like skills and docs to the v2 codebase using read-only v1 access and validation checkpoints, while non-portable source code is stashed for reference to prevent data loss.

Why does the v2 router fail to handle messages after running migrate-v2.sh?▼

The v2 router fails to handle messages when the deterministic migration script leaves unresolved failures, requiring failed step triage to identify and resolve migration blocks before the v2 router can process messages normally.

Does NanoClaw migration support credential masking and non-destructive upgrades?▼

NanoClaw migration supports non-destructive upgrades by enforcing user validation checkpoints, credential masking, and read-only v1 codebase access, ensuring safe migration without data loss or sensitive configuration exposure.

Related Skills

Explore More Education & Research Skills→
BartunekBartunek

migrate-from-v1

Finalize NanoClaw v1 to v2 upgrades by seeding owner, cleaning CLAUDE.local.md, and reconciling container configs.

Community
Advanced
zero-rehqzero-rehq

microservices

Orchestrate cross-repo end-to-end testing with targets, snapshots, and E2E_TRACE verification.

Community
Advanced
VincentChong123VincentChong123

migrate-from-v1

Migrate agent state, permissions, and configuration files from NanoClaw v1 to v2.

Community
Advanced
dchukdchuk
30

migrating-tauri-apps

Migrate Tauri configurations and code from v1 or v2 beta to v2 stable.

Community
Advanced