personal-assistant/skills/migrate/SKILL.md
Migrate your Elle installation between versions. Handles any version-to-version upgrade path with sequential, idempotent steps. Use when updating Elle, when prompted by a version mismatch, or when the user says "migrate Elle" or "upgrade Elle".
npx skillsauth add kenneth-liao/ai-launchpad-marketplace migrateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill handles version-to-version upgrades using sequential, idempotent migration steps. Each version transition has a dedicated reference file containing Check/Action/Verify steps, making migrations safe to re-run on partial completions and easy to extend for future versions.
Primary method: Find the installed version directory.
ls ~/.claude/plugins/cache/ai-launchpad/personal-assistant/
List directories, find the highest version number, and read its .claude-plugin/plugin.json to get the version field.
Fallback fingerprinting (when plugin.json is not reliable):
| Signal | Inferred Version |
|---|---|
| No ~/.claude/.context/ directory | Not installed -- tell user to run /personal-assistant:setup and stop |
| UserPromptSubmit in plugin hooks, no ~/.claude/rules/elle-core.md | v1.0.0 |
| SessionStart in plugin hooks + elle-core.md exists, no ~/.claude/.context/core/improvements.md | v1.9.0 |
| SessionStart + elle-core.md + improvements.md exists | v1.10.0 |
| Full v2 state (migrate skill exists in installed plugin) | v2.0.0 |
Read ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json to get the version of the plugin source being installed.
If current == target: report "Already current. Run /evolve to check for platform upgrades." and stop.
List available migration files from ${CLAUDE_SKILL_DIR}/references/migrations/. Each file is named vX.Y.Z-to-vA.B.C.md.
Parse filenames to build an ordered chain from current version to target version.
Example: if current is v1.10.0 and target is v2.1.0, chain is: v1.10.0 -> v2.0.0, v2.0.0 -> v2.1.0.
For each migration in the chain, read its ## Summary section and present the plan:
Migration path: v1.10.0 -> v2.0.0 -> v2.1.0
Step 1 (v1.10.0 -> v2.0.0):
- Replaces UserPromptSubmit hook with native rules delivery
- ~95% token savings
Step 2 (v2.0.0 -> v2.1.0):
- [summary from file]
Proceed?
Wait for user confirmation before continuing.
Create a timestamped backup before making any changes:
mkdir -p ~/.claude/.context-backups/ && cp -r ~/.claude/.context/ ~/.claude/.context-backups/$(date +%Y%m%d-%H%M%S)/
Verify backup was created:
ls -la ~/.claude/.context-backups/
REQUIRED: DO NOT proceed if backup fails. This is a hard gate.
For each migration in the chain:
${CLAUDE_SKILL_DIR}/references/migrations/## Steps section:
If any step fails:
cp -r ~/.claude/.context-backups/[timestamp]/ ~/.claude/.context/After all migrations complete, verify the final state:
ls -la ~/.claude/rules/elle-core.md
ls ~/.claude/.context/core/
Present final report:
Migration Complete!
Path: vX.Y.Z -> ... -> vA.B.C
Backup: ~/.claude/.context-backups/[timestamp]/
Steps executed: N
Steps skipped (already done): M
Your data: 100% preserved. All personal context untouched.
If rules-affecting changes were made (rules/, elle-core.md, context files), suggest running /sync-context.
Each file at references/migrations/vX.Y.Z-to-vA.B.C.md follows this format:
# Migration: vX.Y.Z -> vA.B.C
## Summary
- [1-3 bullet points describing what this migration does]
## Breaking Changes
- [List any breaking changes, or "None"]
## Steps
### 1. [Step name]
**Check:** `[shell command -- if exits 0, skip this step]`
**Action:** `[shell command to execute]`
**Verify:** `[shell command -- must exit 0 to continue]`
Each step MUST have all three fields (Check, Action, Verify). The Check field makes steps idempotent -- safe to re-run on partially completed migrations.
development
Manage scheduled Claude Code tasks — add (recurring or one-off), list, pause, resume, remove, view results, and test execution of skills, prompts, and scripts with safety controls and notifications. Use when the user mentions scheduling, cron, automated tasks, recurring tasks, background tasks, running something on a schedule, periodic execution, or wants a skill/prompt/script to run automatically at a set time. Cross-platform (macOS, Linux, Windows).
tools
Upgrade a plugin's skills, hooks, and patterns to align with latest Claude Code capabilities and best practices. Use when a plugin needs modernization, after Claude Code updates, or when the user says "upgrade plugin", "modernize plugin", or "update plugin to latest patterns".
tools
Use when reviewing how skills performed during a session, when the user wants to analyze skill invocations and identify improvements, or when the user says "skill retro", "review skills", "how did skills do", "improve this skill", or "skill retrospective".
tools
Run or generate test suites for any skill. Use when testing a skill before deployment, after making changes, before/after plugin upgrades, when validating skill behavior, or when the user says "test skill", "run skill tests", "generate tests for skill", or "check for regressions".