/migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
$ npx -y skills add MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-libraries --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/migrate-skills-between-libraries
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
SKILL.md
migrate-skills-between-libraries.SKILL.mdname: migrate-skills-between-libraries
description: Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
category: workflow
version: 4.1.0
Migrate Skills Between Libraries
Goal
Move skills from one library workspace to another without losing metadata, breaking dependencies, or duplicating entries.
Guardrails
- Always use `--dry-run` before any mutating command in the target workspace.
- Always use `--list` to inspect the source library before importing.
- Always use `--format json` for structured output when scripting migrations.
- Never import skills without checking for name collisions in the target workspace first.
- Always run `build-docs` in the target workspace after migration.
Workflow
Export: Identify skills to migrate from the source library
1. List all skills in the source workspace.
cd /path/to/source-library
npx ai-agent-skills list --format json --fields name,tier,workArea,collections
2. For house copies, note the skill folder paths. For upstream picks, note the installSource.
Import: Add skills to the target workspace
3. For house copies, use `vendor` to copy the skill folder into the target:
cd /path/to/target-library
npx ai-agent-skills vendor /path/to/source-library --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library." --dry-run
npx ai-agent-skills vendor /path/to/source-library --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library."
4. For upstream picks, use `catalog` to re-catalog from the original source:
npx ai-agent-skills catalog <owner>/<repo> --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library." --dry-run
npx ai-agent-skills catalog <owner>/<repo> --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library."
5. Rebuild docs in the target workspace.
npx ai-agent-skills build-docs
6. Validate the target workspace.
npx ai-agent-skills validate
Gotchas
- Skill names must be unique per workspace. Check for collisions before importing.
- House copies are full folder copies — the source and target are independent after migration.
- Upstream picks re-catalog from the original upstream source, not the intermediate library.
- Dependencies (`requires` field) must also be migrated. Check `info --format json` for each skill's dependency graph.
- Collection membership does not transfer automatically. Use `curate --collection <id>` to add migrated skills to target collections.
Read more
name: migrate-skills-between-libraries description: Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another. category: workflow version: 4.1.0
Migrate Skills Between Libraries
Goal
Move skills from one library workspace to another without losing metadata, breaking dependencies, or duplicating entries.
Guardrails
- Always use `--dry-run` before any mutating command in the target workspace.
- Always use `--list` to inspect the source library before importing.
- Always use `--format json` for structured output when scripting migrations.
- Never import skills without checking for name collisions in the target workspace first.
- Always run `build-docs` in the target workspace after migration.
Workflow
Export: Identify skills to migrate from the source library
1. List all skills in the source workspace.
cd /path/to/source-library npx ai-agent-skills list --format json --fields name,tier,workArea,collections
2. For house copies, note the skill folder paths. For upstream picks, note the installSource.
Import: Add skills to the target workspace
3. For house copies, use `vendor` to copy the skill folder into the target:
cd /path/to/target-library npx ai-agent-skills vendor /path/to/source-library --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library." --dry-run npx ai-agent-skills vendor /path/to/source-library --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library."
4. For upstream picks, use `catalog` to re-catalog from the original source:
npx ai-agent-skills catalog <owner>/<repo> --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library." --dry-run npx ai-agent-skills catalog <owner>/<repo> --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library."
5. Rebuild docs in the target workspace.
npx ai-agent-skills build-docs
6. Validate the target workspace.
npx ai-agent-skills validate
Gotchas
- Skill names must be unique per workspace. Check for collisions before importing.
- House copies are full folder copies — the source and target are independent after migration.
- Upstream picks re-catalog from the original upstream source, not the intermediate library.
- Dependencies (`requires` field) must also be migrated. Check `info --format json` for each skill's dependency graph.
- Collection membership does not transfer automatically. Use `curate --collection <id>` to add migrated skills to target collections.
Universal skill installer and package manager for AI coding agents. One command, 12+ runtimes. npx ai-agent-skills
Repo: MoizIbnYousaf/Ai-Agent-Skills
Other skills on moizibnyousaf-ai-agent-skills.
- /ask-questions-if-underspecified
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Open skill - /audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
Open skill - /backend-development
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
Open skill - /best-practices
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
Open skill - /browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
Open skill - /build-workspace-docs
Use when regenerating README.md and WORK_AREAS.md in a managed library workspace. Always dry-run first to preview changes.
Open skill

