skills.rest
Bartunek
BartunekCOMMUNITY
Explore all skills by this author →
Website𝕏@JanBartunekGitHub

migrate-from-v1

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

Updated May 7, 2026
Search Tags:#migration#nanoclaw#v1-to-v2#claude.local.md#container-config#fork-customization
One-click install
npx skills add https://github.com/Bartunek/nanoclaw --skill migrate-from-v1-bartunek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-from-v1
Source: https://github.com/Bartunek/nanoclaw/tree/main/.claude/skills/migrate-from-v1
Command: npx skills add https://github.com/Bartunek/nanoclaw --skill migrate-from-v1-bartunek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill completes the post-migration work after migrate-v2.sh to finalize NanoClaw v1 to v2 upgrades by seeding the owner, cleaning up legacy CLAUDE.local.md files, reconciling container configurations, and porting fork customizations, ensuring a smooth operational handover.

Core Features & Use Cases

  • Guided post-migration workflow that seeds the owner role and sets access controls.
  • Cleans up CLAUDE.local.md and reconciles container configs to reflect v2 architecture.
  • Assists porting customized v1 forks into v2-friendly structures and coordinates with setup logs.

Quick Start

Run the skill after migrate-v2.sh completes to finish the human-in-the-loop migration steps.

Frequently Asked Questions about migrate-from-v1

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

FAQPage Schema
How do I finalize NanoClaw v1 to v2 migration after running migrate-v2.sh?▼

To finalize NanoClaw v1 to v2 migration, complete post-migration tasks like owner seeding, CLAUDE.local.md cleanup, and container config reconciliation using handoff.json and setup logs.

What post-migration steps are required to align a v1 fork with NanoClaw v2 architecture?▼

Porting fork customizations to align with v2 architecture requires reconciling container configs and porting customized v1 forks into v2-friendly structures guided by setup logs.

Do I need to manually clean up CLAUDE.local.md files after upgrading to NanoClaw v2?▼

Yes, cleaning up legacy CLAUDE.local.md files is a required post-migration task to ensure your configuration reflects the v2 architecture properly.

How does the NanoClaw migration handle error recovery during container config reconciliation?▼

NanoClaw migration uses handoff.json and setup logs to guide idempotent, safe execution and provides guardrails for error handling and recovery during container config reconciliation.

When do I need to seed the owner role during the NanoClaw v2 upgrade?▼

Seeding the owner role and setting access controls happens during the post-migration workflow after migrate-v2.sh completes to finalize the operational handover.

Related Skills

Explore More Software Engineering Skills→
chiptoe-svgchiptoe-svg

migrate-from-v1

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

Community
Advanced
tharunramagiritharunramagiri

migrate-nanoclaw

Extract NanoClaw fork customizations into a replayable migration guide.

Community
Advanced
harnessharness
80

manage-slos

Correlate deployments with incidents and generate SRM runbooks via Harness MCP v2.

Official
Advanced
VincentChong123VincentChong123

migrate-from-v1

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

Community
Advanced