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.
What this skill does
# 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
Related in workflow
absolute-work
IncludedEnd-to-end, phase-gated software development lifecycle for AI agents. Turns a ticket, task, plan, or migration into a validated design, a dependency-graphed task board, and verified code. Triggers on "build this end-to-end", "plan and build", "break this into tasks", "pick up this ticket", "grill me on this", "run this migration", "absolute-work this", or any multi-step development task. Relentlessly interviews to a shared design, writes a reviewed spec, decomposes into atomic tasks on a persistent markdown board, then peels tasks one safe wave at a time with test-first verification. Handles features, bugs, refactors, greenfield projects, planning breakdowns, and migrations.
absolute-simplify
IncludedAutonomously simplifies code in your working changes or targeted files. Detects staged or unstaged git changes, analyzes for simplification opportunities following clean code and clean architecture principles, applies improvements directly, runs tests to verify nothing broke, and shows a structured summary with reasoning. Triggers on "simplify this", "refactor this", "clean up my changes", "absolute-simplify", "simplify my code", "make this cleaner", "tidy this up", "reduce complexity", "flatten this", "remove dead code", or when code needs clarity improvements, nesting reduction, or redundancy removal. Language-agnostic at base with deep opinions for JS/TS/React, Python, and Go.
sentry-sdk-upgrade
IncludedUpgrade the Sentry JavaScript SDK across major versions. Use when asked to upgrade Sentry, migrate to a newer version, fix deprecated Sentry APIs, or resolve breaking changes after a Sentry version bump.
when-using-advanced-swarm-use-swarm-advanced
IncludedAdvanced swarm patterns with dynamic topology switching and self-organizing behaviors for complex multi-agent coordination
development-workflow
IncludedDetailed development workflow with modular patterns for git, review, testing, and deployment.
project-execution
IncludedExecutes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.