01
Why v2 needs a real migration
The current README says v2 renames 17 skills and consolidates page-cro plus form-cro into cro. A normal reinstall can therefore leave stale v1 folders next to the new canonical names.
- Back up any local custom skill edits before deletion.
- Record the current repository commit or installed version.
- Use the live upstream README as the rename source instead of an old article copy.
02
Clean up legacy names
Examples in the current migration map include analytics-tracking to analytics, paid-ads to ads, schema-markup to schema, social-content to social and launch-strategy to launch. The exact list can evolve.
- Remove only legacy folders you have verified are upstream copies.
- Reconcile custom local changes before cleanup.
- Remember that page-cro and form-cro both converge into the broader cro skill.
03
Move shared product context deliberately
The current structure centers shared product context on .agents/product-marketing.md. Older Claude-specific paths may still be checked as fallbacks, but new installations should follow the current cross-agent layout.
- Do not overwrite two different legacy context files blindly.
- Keep one canonical product-marketing document after reconciliation.
- Review the git diff so the migration can be audited or rolled back.
04
Reinstall and verify
Reinstall with the current supported method, then inspect installed folders and run one low-risk task through a renamed skill. Confirm the agent reads the new product-marketing context.
- Check old names are gone and new names are present.
- Test at least one renamed workflow.
- Commit the migration after verifying behavior so rollback remains straightforward.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.