migrate-from-v1 Skill
Finish migrating a NanoClaw v1 install into v2. Run after bash migrate-v2.sh completes. Seeds the owner, cleans up CLAUDE.local.md files, reconciles container configs, and helps port custom v1 code. Triggers on "migrate from v1", "finish migration", "v1 migration". Published by microsoft in amplifier-app-nanoclaw.
What is migrate-from-v1 Skill?
Finish migrating a NanoClaw v1 install into v2. Run after bash migrate-v2.sh completes. Seeds the owner, cleans up CLAUDE.local.md files, reconciles container configs, and helps port custom v1 code. Triggers on "migrate from v1", "finish migration", "v1 migration". Published by microsoft in amplifier-app-nanoclaw. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Design and media
- Data analysis use cases
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use migrate-from-v1 Skill
- Use it for data analysis.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-nanoclaw
- Skill file: .claude/skills/migrate-from-v1/SKILL.md
What it does
Finish migrating a NanoClaw v1 install into v2. Run after bash migrate-v2.sh completes. Seeds the owner, cleans up CLAUDE.local.md files, reconciles container configs, and helps port custom v1 code. Triggers on "migrate from v1", "finish migration", "v1 migration".
Skill instructions
Finish v1 → v2 migration bash migrate-v2.sh already ran the deterministic migration. It handled: - .env keys merged - v2 DB seeded (agentgroups, messaginggroups, 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 messaginggroups - Container skills copied - Container image built Your job is the parts that need human judgment: triage any failed steps, seed the owner, clean up CLAUDE.local.md files, reconcile configs, and port any fork customizations. Read logs/setup-migration/handoff.json first — it has overallstatus, 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 skil
Explore related resources
Frequently asked questions
What is migrate-from-v1?
migrate-from-v1 is a open-source AI agent skill with Copy skill directory. Finish migrating a NanoClaw v1 install into v2. Run after bash migrate-v2.sh completes. Seeds the owner, cleans up CLAUDE.local.md files, reconciles container configs, and helps port custom v1 code.
Who is migrate-from-v1 best for?
migrate-from-v1 is best for reusing agent instructions, scripts, and references, data analysis workflows, design and media workflows.
How do I install migrate-from-v1?
Install or run migrate-from-v1 using Copy skill directory. Check migrate-from-v1 for the latest setup command.
Is migrate-from-v1 actively maintained?
migrate-from-v1 may need a closer maintenance check before production use.
Auto-fetched from GitHub.
