← ClaudeAtlas

migratelisted

Mirror the user's laptop dev environment onto this box from a shellteam-mirror tarball. Use when the user mentions mirroring/migrating their local setup (Mac, WSL, laptop), moving in, the import wizard, or a shellteam-mirror-*.tar.gz file (often in ~/.mirror-inbox/).
sebderhy/shellteam · ★ 4 · AI & Automation · score 77
Install: claude install-skill sebderhy/shellteam
# Environment Mirror — migrate a laptop setup onto this box The user ran the import wizard (`mirror-import.sh`) or the inventory script (`mirror-inventory.sh`) on their laptop. A `shellteam-mirror-*.tar.gz` is now on this box — wizard uploads land in `~/.mirror-inbox/`, manual uploads usually in `~/`. Your job: make this box feel like their machine — same tools, same shell, same agent config and logins, same repos, same conversations — adapted honestly to Ubuntu. This is a *functional* migration, not a byte copy. If no tarball exists yet, point them at the box's Settings tab ("Import your laptop") — it mints the exact wizard command with upload credentials baked in. The manual fallback fetches from THIS box (it serves the scripts itself, at exactly its installed version — never point them at GitHub for these), with `<box-url>` being this box's dashboard URL: ``` curl -fsSLO <box-url>/api/mirror/mirror-inventory.sh bash mirror-inventory.sh ``` ## Ground rules 1. **Never overwrite an existing file on this box.** Merge additively; when a real conflict exists, back the original up to `<file>.pre-mirror` and say so. 2. **The tarball may contain a `secure/` directory** (agent logins, MCP tokens, chat history, project `.env` files) — only when the user explicitly ticked those in the wizard for a direct upload to their own box. Treat it as live credentials: install with `0600` permissions, and when you're done **delete the tarball and every extracted copy of `s