skill-installer

To install GitHub skills from a repository URL, run the installer script with the repo and path arguments to fetch and extract the skill into the local .grok/skills directory. The tool validates the presence of a SKILL.md file before completing the installation.

Yes, you can install skills from private GitHub repositories using git sparse-checkout with token-based authentication. The installer falls back to this method automatically when ZIP download fails for private repos requiring authentication.

Installing skills via ZIP download fetches a public repository archive for fast extraction, while sparse-checkout handles private repositories by cloning only the specified skill path. ZIP is attempted first for speed, with sparse-checkout as the fallback for private access.

No, the skill installer enforces a non-overwrite policy for existing skills in the local directory. If a skill already exists at the target path, the installation will fail to prevent accidental data loss or conflicting configurations.

GitHub skill installation fails with a missing SKILL.md validation error when the target repository path does not contain this required metadata file. The installer checks for SKILL.md to verify the directory is a valid, structured skill before proceeding.

Yes, you need network access to fetch repository files and git installed for private repo sparse-checkout fallback. Public repos use ZIP download and extraction, but private repositories require git operations with token-based authentication.