Migration
Structured 10-phase workflow for safe, verifiable migrations — discovery, blast radius, rollback plan, execute, verify
- What
- Structured 10-phase workflow for safe, verifiable migrations — discovery, blast radius, rollback plan, execute, verify
- Cost
- Free
- Needs
- a source and a target (framework, library, API) for the migration; the source code and target docs available to read
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a structured 10-phase migration workflow from the Caveman repo: Phase 0/1 discovery (is this even a migration? read the source and target first, check if a codemod already exists), Phase 2 blast radius (every consumer, every test, every deployment artifact, every monitoring rule, every dependent migration), Phase 3 rollback planning (when do you give up? revert commands planned before touching code), Phase 4 plan, Phase 5 execute in small verified steps, Phase 6/7 verify then verify again (the "trust but verify" gates), Phase 8 review. By @juliusbrussee, listed here with credit to its creator. Honest caveats: a methodology, not a shortcut — it deliberately makes migrations boring and slow; the rollback plan is written before any code changes. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Migration is a free Muse skill offering a structured ten-phase workflow for safe, verifiable migrations, covering discovery, blast radius, rollback plan, execution and verification. It starts with discovery, asking whether this is even a migration and reading source and target first, then maps blast radius across every consumer, test and deployment artifact before executing.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 2e08b91Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a source and a target (framework, library, API) for the migration; the source code and target docs available to read Install "Migration" for me. Structured 10-phase workflow for safe, verifiable migrations — discovery, blast radius, rollback plan, execute, verify Repository: https://github.com/juliusbrussee/caveman Pinned version: install the code at commit 2e08b9177c07bb7249a8a2d1a6758e5db281d002 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the juliusbrussee-migration skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "juliusbrussee-migration". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 2e08b91 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.