migrate-skills-between-libraries

1# Migrate Skills Between Libraries
2 
3## Goal
4 
5Move skills from one library workspace to another without losing metadata, breaking dependencies, or duplicating entries.
6 
7## Guardrails
8 
9- Always use `--dry-run` before any mutating command in the target workspace.
10- Always use `--list` to inspect the source library before importing.
11- Always use `--format json` for structured output when scripting migrations.
12- Never import skills without checking for name collisions in the target workspace first.
13- Always run `build-docs` in the target workspace after migration.
14 
15## Workflow
16 
17### Export: Identify skills to migrate from the source library
18 
191. List all skills in the source workspace.
20 
21```bash
22cd /path/to/source-library
23npx ai-agent-skills list --format json --fields name,tier,workArea,collections
24```
25 
262. For house copies, note the skill folder paths. For upstream picks, note the installSource.
27 
28### Import: Add skills to the target workspace
29 
303. For house copies, use `vendor` to copy the skill folder into the target:
31 
32```bash
33cd /path/to/target-library
34npx ai-agent-skills vendor /path/to/source-library --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library." --dry-run
35npx ai-agent-skills vendor /path/to/source-library --skill <name> --area <workArea> --branch <branch> --why "Migrated from source library."
36```
37 
384. For upstream picks, use `catalog` to re-catalog from the original source:
39 
40```bash
41…