ask-questions-if-under…
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
Claude Code
$ npx -y skills add MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-libraries --agent claude-code
Codex
$ npx skills add MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-libraries -a codex -y
Cursor
$ npx skills add MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-libraries -a cursor -y
Gemini CLI
$ npx skills add MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-libraries -a gemini-cli -y
GitHub Copilot
$ npx skills add MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-libraries -a github-copilot -y
OpenCode
$ npx skills add MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-libraries -a opencode -y
Windsurf
$ npx skills add MoizIbnYousaf/Ai-Agent-Skills --skill migrate-skills-between-libraries -a windsurf -y
name: migrate-skills-between-libraries description: Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another. category: workflow version: 4.1.0
Move skills from one library workspace to another without losing metadata, breaking dependencies, or duplicating entries.
1. List all skills in the source workspace.
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.
3. 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."
4. 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."
5. Rebuild docs in the target workspace.
npx ai-agent-skills build-docs
6. Validate the target workspace.
npx ai-agent-skills validate
Universal skill installer and package manager for AI coding agents. One command, 12+ runtimes. npx ai-agent-skills
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs…
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database…
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper…
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to…
Use when regenerating README.md and WORK_AREAS.md in a managed library workspace. Always dry-run first to preview changes.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.