MoizIbnYousafMoizIbnYousaf/Ai-Agent-Skills/skills/migrate-skills-between-libraries/SKILL.md

migrate-skills-between-libraries

Skill1.1k starsChanged 8 months agoMITView on GitHub

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

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Always use --dry-run before any mutating command in the target workspace.
line 16
Very specific:
Always use --list to inspect the source library before importing.
line 17
Very specific:
Always use --format json for structured output when scripting migrations.
line 18
Distinctive:
Never import skills without checking for name collisions in the target workspace first.
line 19
Very specific:
Always run build-docs in the target workspace after migration.
line 20

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

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

List all skills in the source workspace.

cd /path/to/source-library
npx ai-agent-skills list --format json --fields name,tier,workArea,collections

For house copies, note the skill folder paths. For upstream picks, note the installSource.

Import: Add skills to the target workspace

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."

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."

Rebuild docs in the target workspace.

npx ai-agent-skills build-docs

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.

Download now (ZIP)

Other versions2 projects use a version of this.
Word for word · 2
skillcreatorai/Ai-Agent-Skills★ 1.1k100% same
MoizIbnYousaf/ai-agent-skills★ 1.1k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- ask-questions-if-underspecifiedSkill
- audit-library-healthSkill
- backend-developmentSkill
- best-practicesSkill
- browse-and-evaluateSkill
- build-workspace-docsSkill
- changelog-generatorSkill
- code-documentationSkill
- content-research-writerSkill
- curate-a-team-librarySkill
- database-designSkill
- install-from-remote-librarySkill
- llm-application-devSkill
- review-a-skillSkill
- share-a-librarySkill
- update-installed-skillsSkill
- verification-agentSkill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free