Install from remote library
Skill MoizIbnYousaf/Ai-Agent-Skills/skills/install-from-remote-library
Universal skill installer and package manager for AI coding agents. One command, 12+ runtimes. npx ai-agent-skills
npx -y skills add MoizIbnYousaf/Ai-Agent-Skills --skill install-from-remote-libraryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Use when installing skills from a shared ai-agent-skills library repo. Inspect with `--list` first, prefer `--collection`, and preview with `--dry-run` before installing.
SKILL.md
2.1 KB, as published. Nobody here has run it
Install From Remote Library
Goal
Install from a shared library repo without guessing, over-installing, or skipping the preview step.
Invariants
- Always inspect the remote library first with
install <source> --list. - Prefer
--collectionwhen the library clearly exposes a starter pack or focused bundle. - Always run
--dry-runbefore the real install. - Keep the install small. Do not pull a whole library when the user only needs a narrow slice.
Workflow
- Inspect the source library.
npx ai-agent-skills install <owner>/<repo> --list
- Choose the smallest fitting target.
- Prefer
--collection starter-packor another named collection when it matches the user's need. - Use
--skill <name>only when the user needs one specific skill or the library has no useful collection. - Do not combine
--collectionand--skill.
- Preview the install plan before mutating anything.
npx ai-agent-skills install <owner>/<repo> --collection starter-pack --dry-run -p
or
npx ai-agent-skills install <owner>/<repo> --skill <skill-name> --dry-run -p
- If the plan looks right, run the real install with the same scope.
npx ai-agent-skills install <owner>/<repo> --collection starter-pack -p
Decision Rules
- If the library has a curated collection that already matches the user's stack, use it.
- If the remote library is empty or the list output is unclear, stop and report that instead of guessing.
- If the install path throws an
ERROR/HINT, surface that verbatim and follow the hint before retrying. - If the user is exploring a large library, keep them in browse mode first rather than installing immediately.
Done
Return:
- what source library you inspected
- which collection or skill you chose
- the dry-run result
- the exact final install command you used