Skip to content
Development
Skill

/install-from-remote-library

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.

From plugin
ai-agent-skills
1.1k17 skills3 agents
Install
$ npx -y skills add skillcreatorai/ai-agent-skills --skill install-from-remote-library --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/install-from-remote-library

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

install-from-remote-library.SKILL.md
name: install-from-remote-library
description: 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.
category: workflow
version: 4.1.0

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 `--collection` when the library clearly exposes a starter pack or focused bundle.
  • Always run `--dry-run` before the real install.
  • Keep the install small. Do not pull a whole library when the user only needs a narrow slice.

Workflow

1. Inspect the source library.

npx ai-agent-skills install <owner>/<repo> --list

2. Choose the smallest fitting target.

  • Prefer `--collection starter-pack` or 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 `--collection` and `--skill`.

3. 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

4. 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
Read more
Ships withai-agent-skills

Universal skill installer and package manager for AI coding agents. One command, 12+ runtimes. npx ai-agent-skills

Get the whole plugin