Install Skill Pack

Install reviewed skills from the user's Git repository. The default path passes the bare source to the CLI and follows the remote's default branch. Branch and commit pins are optional.

Install globally by default; run a project-local install only when the user explicitly requests one. Select the target agents in this order: the agents the user names for this install; otherwise a default agent list the user has recorded in their instruction files; otherwise the harnesses the CLI detects on this host, confirmed once with the user before installing. Pass each target as an explicit --agent. Never use the broad --all option or omit --agent: without it the CLI picks targets itself and, when it detects no harness, installs to every agent it knows. Let the CLI manage the canonical global package and agent-facing links.

Review the source directly. Third-party scans are optional; a missing scanner result is neither a pass nor a blocker.

Quick Path

1. Check prerequisites: Node with npm and npx at the version the resolved Skills CLI release declares (releases 1.5.23 through 1.7.1 require Node 22.20.0 or later), git, python3 for the rename script, and network access to the repository host and the npm registry. If a tool is missing or too old, stop and report it rather than installing it.

   Resolve the repository source and selected skill names. Accept GitHub shorthand, a full repository URL, or another cloneable Git URL. Read references/skills-cli-usage.md for target selection and detection, the current CLI contract, symlink mode, and per-agent verification. Resolve names from the current request and already-established session scope, including a skill just published for installation. If that leaves the selection unclear, list the repository's skills first; install every package only when the user explicitly requested the complete pack.

2. Select one revision mode:

   • Default: no revision input. Use the remote default branch at its latest commit and keep the CLI source bare, for example owner/repo.
   • Branch: append #<branch> to the CLI source.
   • Commit: require an exact full commit ID and use the detached-checkout path below. Do not append a raw commit ID to the CLI source.