migrate-skills-between-libraries

Migrate skills between ai-agent-skills library workspaces using vendor and catalog commands.

1.1k|131|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/skillcreatorai/Ai-Agent-Skills --skill migrate-skills-between-libraries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-skills-between-libraries
Source: https://github.com/skillcreatorai/Ai-Agent-Skills/tree/main/skills/migrate-skills-between-libraries
Command: npx skills add https://github.com/skillcreatorai/Ai-Agent-Skills --skill migrate-skills-between-libraries

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ai-agent-skills.

What problem does it solve?

Moving skills between library workspaces risks losing metadata, breaking dependencies, and creating duplicate entries. This Skill provides a guarded export-and-import workflow for upgrading from a personal library to a team library or consolidating workspaces.

Core Features & Use Cases

  • Safe Export and Inspection: Lists source workspace skills with --format json to capture names, tiers, work areas, and collections before migrating.
  • Dual Import Paths: Uses vendor for house copies (full folder copies) and catalog for upstream picks (re-cataloged from the original source).
  • Collision and Dependency Checks: Enforces dry-run previews, name-collision checks, and dependency graph inspection via info --format json.
  • Use Case: You maintain a personal ai-agent-skills library and want to move 20 curated skills into a shared team workspace without losing provenance notes or duplicating entries.

Quick Start

Migrate all skills from my personal library at ~/my-library into the team workspace at ~/team-library, checking for name collisions first.

Frequently Asked Questions about migrate-skills-between-libraries

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate skills between ai-agent-skills workspaces?

List skills in the source workspace with `npx ai-agent-skills list --format json`, then import house copies with `vendor` and upstream picks with `catalog` in the target workspace. Always run with `--dry-run` first, then rebuild docs and validate.

What is the difference between vendor and catalog commands?

The `vendor` command copies a skill folder fully into the target workspace, making source and target independent. The `catalog` command re-catalogs an upstream pick from its original source repository rather than copying files.

Do skill dependencies transfer automatically during migration?

No, dependencies declared in a skill's `requires` field must be migrated separately. Inspect each skill's dependency graph with `info --format json` and migrate required skills alongside the primary ones.

Why does skill import fail with a name collision error?

Skill names must be unique per workspace, so importing a skill whose name already exists in the target fails. Check the target workspace with `--list` before importing and rename or skip conflicting entries.

Do collection memberships carry over when migrating skills?

No, collection membership does not transfer automatically between workspaces. After migration, use `curate --collection <id>` in the target workspace to add migrated skills to the appropriate collections.