diff --git a/skills/setup-changesets/SKILL.md b/skills/setup-changesets/SKILL.md
index dd74e4c..c243eec 100644
--- a/skills/setup-changesets/SKILL.md
+++ b/skills/setup-changesets/SKILL.md
@@ -11,10 +11,7 @@ description: "Use this skill when setting up changesets, release CI, or migratin
 - Adding or fixing the CI release workflow (`changesets/action` on GitHub, or direct `version`/`publish` elsewhere)
 - Migrating from semantic-release, release-it, lerna, release-please, or similar tools
 
-**Not this skill:**
-
-- Adding a changeset to the current PR → use **`add-changeset`**
-- GitHub branch protection / Dependabot only → use **`setup-github-repo`** (repobuddy main repo)
+Not this skill: adding a changeset to an existing PR → use **`add-changeset`** instead.
 
 Trigger phrases: `'add changesets'`, `'set up releases'`, `'configure versioning'`, shared `<org>/.github` release workflow.
 
@@ -293,10 +290,4 @@ ls .changeset/
 gh workflow list   # GitHub only
 ```
 
-## After setup
-
-1. Developers add changeset files via the **`add-changeset`** skill (do not duplicate its bump/summary rules here).
-2. PR merges to main → CI opens/updates **Version Packages** PR (GitHub) or version+publishes in one run (other CI).
-3. Merge Version Packages PR → publish to npm.
-
-Do not manually edit `CHANGELOG.md` or versions on the Version Packages PR.
+Tell the user to add future changesets via the **`add-changeset`** skill. Never manually edit `CHANGELOG.md` or version bumps — the Version Packages PR is fully generated.
diff --git a/skills/setup-changesets/references/migration/lerna.md b/skills/setup-changesets/references/migration/lerna.md
index 4807ab3..22cca76 100644
--- a/skills/setup-changesets/references/migration/lerna.md
+++ b/skills/setup-changesets/references/migration/lerna.md
@@ -1,7 +1,9 @@
 # Migrate from lerna
 
-1. Remove packages: `<pm> remove lerna`
-2. Delete config files: `lerna.json`
+Lerna is a monorepo task runner (`lerna run`, `lerna exec`) as well as a release tool — keep it installed and disable only the versioning/publishing parts.
+
+1. Keep lerna installed — `lerna run` and `lerna exec` may still be in use
+2. In `lerna.json`, remove the `command.version` and `command.publish` sections if present; keep `packages`, `npmClient`, and any task-runner config
 3. Remove any `"lerna publish"` or `"lerna version"` calls from scripts in `package.json`
 4. In CI config, find and remove the step running `lerna publish`
 5. Secrets: `GH_TOKEN` / `GITHUB_TOKEN` and `NPM_TOKEN` reusable