install-from-remote-library
Skill1.1k starsChanged 8 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Always inspect the remote library first with install <source> --list.
- Very specific: line 17
Prefer --collection when the library clearly exposes a starter pack or focused bundle.
- Very specific: line 18
Always run --dry-run before the real install.
- Distinctive: line 19
Keep the install small. Do not pull a whole library when the user only needs a narrow slice.
- Very specific: line 31
Prefer --collection starter-pack or another named collection when it matches the user's need.
- Very specific: line 32
Use --skill <name> only when the user needs one specific skill or the library has no useful collection.
- Very specific: line 33
Do not combine --collection and --skill.
- Distinctive: line 47
If the plan looks right, run the real install with the same scope.
- Distinctive: line 55
If the library has a curated collection that already matches the user's stack, use it.
- Distinctive: line 56
If the remote library is empty or the list output is unclear, stop and report that instead of guessing.
- Very specific: line 57
If the install path throws an ERROR / HINT, surface that verbatim and follow the hint before retrying.
- Distinctive: line 58
If the user is exploring a large library, keep them in browse mode first rather than installing immediately.
≈ “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.
Files
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 -por
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 -pDecision 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
Trending
More talk lately.thin dataabout the whole repository
Who's talking about MoizIbnYousaf/Ai-Agent-Skills
- ProSkillsMD/proskills“[Candidate] moizibnyousaf/ai-agent-skills/skills/backend-development - backend-development”GitHub · Oct 9, 2026
- ProSkillsMD/proskills“[Candidate] moizibnyousaf/ai-agent-skills/skills/audit-library-health - audit-library-health”GitHub · Oct 9, 2026
- ProSkillsMD/proskills“[Candidate] moizibnyousaf/ai-agent-skills/skills/ask-questions-if-underspecified - …”GitHub · Oct 9, 2026
- sudosubin/agents.nix“agent-skills.github.moizibnyousaf.ai-agent-skills: init at 4.3.2”GitHub · Sep 30, 2026
The biggest 4 of 4 mentions linking to the repository that our crawl found. Each line is their own headline.
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
- llm-application-devSkill
- migrate-skills-between-librariesSkill
- 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.

