I
install-from-remote-library
About install-from-remote-library
A reusable skill for installing a focused selection from a shared ai-agent-skills library. It emphasizes inspecting available options, choosing a collection or individual skill, and previewing the install before making changes.
Key features
- 01List available remote library contents
- 02Choose a collection or single skill
- 03Preview installation with dry-run
- 04Keep installs limited to the requested scope
- 05Report the chosen source and install command
Use cases
- 01Install a matching starter collection
- 02Add one skill from a shared library
- 03Explore a library before installing
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ moizibnyousaf/ ai-agent-skills --skill install-from-remote-libraryAfter installing, type/install-from-remote-libraryin Claude Code to confirm it loaded.
Details
From the project READMEInstall 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
Comments
Markdown supported