Aiconfig Migrate
Resolve stale prompts that still call aiconfig-migrate by redirecting to the renamed migrate skill without running deprecated logic.
Overview
Aiconfig-migrate is a journey-wide agent skill that only redirects deprecated references to the migrate skill—usable whenever a solo builder needs to fix stale skill names before committing to automation changes.
Install
npx skills add https://github.com/launchdarkly/agent-skills --skill aiconfig-migrateWhat is this skill?
- Hard stop: do not follow instructions in this skill or perform migration from here
- Single redirect target: invoke the migrate skill for current Apache-2.0 instructions
- Preserves old slug aiconfig-migrate so saved prompts and automation do not break silently
- Explicit deprecation note in frontmatter (version 0.1.0)
- Renamed to migrate; version 0.1.0 in metadata
Adoption & trust: 1.2k installs on skills.sh; 16 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Old docs and prompts still invoke aiconfig-migrate, so agents might run outdated or empty instructions instead of the current migrate skill.
Who is it for?
Updating legacy skill slugs in agent configs, READMEs, or saved workflows without guessing the new name.
Skip if: Performing AI config or LaunchDarkly migration work—use migrate exclusively.
When should I use this skill?
An old reference, saved prompt, or automation still points at aiconfig-migrate.
What do I get? / Deliverables
The agent stops and invokes migrate, and you update references from aiconfig-migrate to migrate.
- Updated skill invocation pointing at migrate
- No migration artifacts from this stub
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Rename a skill slug in your repo’s SKILL.md index without breaking agents that still list aiconfig-migrate.
Pre-release check that deployment docs reference migrate, not the deprecated slug.
Audit saved Claude Code commands and replace aiconfig-migrate with migrate.
How it compares
Alias stub, not a second migration implementation alongside migrate.
Common Questions / FAQ
Who is aiconfig-migrate for?
Anyone with automation or prompts that still reference the old aiconfig-migrate slug who needs a clear redirect to migrate.
When should I use aiconfig-migrate?
Whenever an agent loads this skill by mistake during Operate iteration on configs, or when auditing skill names before Ship or Grow documentation updates—then immediately switch to migrate.
Is aiconfig-migrate safe to install?
It is intentionally non-functional beyond a redirect; still review the Security Audits panel on this Prism page before adding any skill to your agent bundle.
Workflow Chain
Then invoke: migrate
SKILL.md
READMESKILL.md - Aiconfig Migrate
# Deprecated — renamed to `migrate` This skill has been renamed. **Do not follow any instructions here and do not perform the task from this skill.** Invoke the **`migrate`** skill instead — it contains the current, complete instructions. If you arrived here from an old reference (documentation, a saved prompt, or automation), update it from `aiconfig-migrate` to `migrate`.