Agent skill

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.

MoizIbnYousafgithub.com/MoizIbnYousafGitHub ↗
claude-codecodexcursorMIT
Install
npx skills add MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-libraries --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 3 KB
Bundled scripts: none
Version: 4.1.0
Path: skills/migrate-skills-between-libraries/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,114
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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. ```bash 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: ```bash 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

What's inside
Steps it walks through
  1. Goal
  2. Guardrails
  3. Workflow
  4. Export: Identify skills to migrate from the source library
  5. Import: Add skills to the target workspace
  6. Gotchas
Commands it runs
cd /path/to/source-library
npx ai-agent-skills list --format json --fields name,tier,workArea,collections
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."
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-docs
npx ai-agent-skills validate
More from Ai-Agent-Skills
All skills →
About this skill
What does the migrate-skills-between-libraries skill do?

Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.

How do I install it?

Run `npx skills add MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-libraries --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From MoizIbnYousaf/Ai-Agent-Skills, a repository with 1,114 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going