migrate-from-v1 SKILL.md skillA
migrate-from-v1 from nanocoai/nanoclaw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nanocoai/nanoclaw/migrate-from-v1@git:20260819.2cd7b53Pins git:20260819.2cd7b53 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nanocoai/nanoclaw
- Path
.claude/skills/migrate-from-v1/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260819.2cd7b53, committed Aug 19, 2026
- First version recorded
- May 2, 2026
- Size
- 11,455 bytes
- Repository stars
- 31,085
- License
- MIT
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".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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: …
Read the whole file at its exact version.
How to install
mdr add nanocoai/nanoclaw/migrate-from-v1@sha256:2fdcde8b58a7797bThe line at the top of this page pins the label git:20260819.2cd7b53, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_iydfb647tqd6qb7c)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 2, 2026 and Aug 19, 2026, about one every 27 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260819.2cd7b53 latest | 2026-08-19 | 2cd7b53 | 11,455 B | A | view · diff |
| git:20260715.25b820c | 2026-07-15 | 25b820c | 11,390 B | A | view · diff |
| git:20260715.76d941b | 2026-07-15 | 76d941b | 11,356 B | A | view · diff |
| git:20260606.14dba9b | 2026-06-06 | 14dba9b | 13,506 B | A | view · diff |
| git:20260502.7922a19 | 2026-05-02 | 7922a19 | 12,309 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11455 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nanocoai/nanoclaw · 31,085 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iydfb647tqd6qb7c GET https://markdownregistry.com/api/v1/resolve?ref=nanocoai/nanoclaw/migrate-from-v1 GET https://markdownregistry.com/api/v1/blob/2fdcde8b58a7797bdc5001da88cd887bd38f83f3349384da530e3ad10938262c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.