install-from-remote-library

$npx mdskill add MoizIbnYousaf/Ai-Agent-Skills/install-from-remote-library

Install skills from a shared library with preview and minimal scope.

  • Avoids guessing or over-installing from a remote skill library.
  • Depends on the npx ai-agent-skills CLI tool.
  • Inspects library contents and selects the smallest fitting target.
  • Runs a dry-run preview before executing the actual install.

SKILL.md

.github/skills/install-from-remote-libraryView on GitHub ↗
---
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.

```bash
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.

```bash
npx ai-agent-skills install <owner>/<repo> --collection starter-pack --dry-run -p
```

or

```bash
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.

```bash
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

More from MoizIbnYousaf/Ai-Agent-Skills

SkillDescription
ask-questions-if-underspecifiedClarify requirements before implementing. Do not use automatically, only when invoked explicitly.
audit-library-healthUse when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
backend-developmentBackend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
browse-and-evaluateUse when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
build-workspace-docsUse when regenerating README.md and WORK_AREAS.md in a managed library workspace. Always dry-run first to preview changes.
code-documentationWriting effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
curate-a-team-libraryUse when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful `whyHere` notes, and create a starter pack once the first pass is solid.
llm-application-devBuilding applications with Large Language Models - prompt engineering, RAG patterns, and LLM integration. Use for AI-powered features, chatbots, or LLM-based automation.
migrate-skills-between-librariesUse when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
review-a-skillUse when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.