Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
75
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Move skills from one library workspace to another without losing metadata, breaking dependencies, or duplicating entries.
--dry-run before any mutating command in the target workspace.--list to inspect the source library before importing.--format json for structured output when scripting migrations.build-docs in the target workspace after migration.cd /path/to/source-library
npx ai-agent-skills list --format json --fields name,tier,workArea,collectionsvendor 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."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."npx ai-agent-skills build-docsnpx ai-agent-skills validaterequires field) must also be migrated. Check info --format json for each skill's dependency graph.curate --collection <id> to add migrated skills to target collections.039ad59
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.