install-from-remote-library

1# Install From Remote Library
2 
3## Goal
4 
5Install from a shared library repo without guessing, over-installing, or skipping the preview step.
6 
7## Invariants
8 
9- Always inspect the remote library first with `install <source> --list`.
10- Prefer `--collection` when the library clearly exposes a starter pack or focused bundle.
11- Always run `--dry-run` before the real install.
12- Keep the install small. Do not pull a whole library when the user only needs a narrow slice.
13 
14## Workflow
15 
161. Inspect the source library.
17 
18```bash
19npx ai-agent-skills install <owner>/<repo> --list
20```
21 
222. Choose the smallest fitting target.
23 
24- Prefer `--collection starter-pack` or another named collection when it matches the user's need.
25- Use `--skill <name>` only when the user needs one specific skill or the library has no useful collection.
26- Do not combine `--collection` and `--skill`.
27 
283. Preview the install plan before mutating anything.
29 
30```bash
31npx ai-agent-skills install <owner>/<repo> --collection starter-pack --dry-run -p
32```
33 
34or
35 
36```bash
37npx ai-agent-skills install <owner>/<repo> --skill <skill-name> --dry-run -p
38```
39 
404. If the plan looks right, run the real install with the same scope.
41 
42```bash
43npx ai-agent-skills install <owner>/<repo> --collection starter-pack -p
44```
45 
46## Decision Rules
47 
48- If the library has a curated collection that already matches the user's stack, use it.
49- If the remote library is empty or the list output is unclear, stop and report that instead of guessing.
50…