sincecutoff.com
← all changes

gh skill manages and publishes agent skills

Introduced 2026-04-16 · score 0.97

HOW TO USE IT

When managing a skill from a GitHub repository, use `gh skill` to search, preview, install, or update it; to validate or publish your own skills, run `gh skill publish` from the local repository. Installation can target an agent and project or user scope.

gh skill install <owner>/<repo> <skill> --agent <agent> --scope <project|user>
gh skill update --all
gh skill publish --dry-run

WHY THIS HELPS

Manage or publish an agent skill from a GitHub repository for a supported coding agent host.

REQUIREMENTS AND LIMITATIONS

  • Version: v2.90.0
  • Availability: Public Preview; subject to change without notice.
  • <owner>/<repo> (required): GitHub repository containing the skill.
  • <skill>: Skill name, namespaced name, or repository path; required for a specific skill unless using `--all`.
  • --agent <agent>: Select the target agent; install documentation gives supported values.
  • --scope <project|user>: Choose installation scope; default is `project`.
  • --pin <tag-or-SHA>: Pin installation to a Git tag or commit SHA.
  • --all: Update all installed skills without prompting.
  • --dry-run: Validate publishing without publishing.
  • Prerequisite: Install command requires a GitHub repository in `OWNER/REPO` format; skills are discovered from `SKILL.md` files.
  • Prerequisite: Publishing validates skills in a local repository and creates a GitHub release after validation.
  • Prerequisite: The release identifies `gh skill` as public preview in GitHub CLI v2.90.0.
  • Skills are automatically installed to the correct directory for the agent host.
  • Supported hosts are GitHub Copilot, Claude Code, Cursor, Codex, Gemini CLI, and Antigravity.
  • Docs conflict: The current install manual lists additional agent hosts beyond the six named in the v2.90.0 release note; the manual reflects a newer, broader host list.
  • Docs conflict: The current publish manual describes release creation but does not document the release note's auto-push of unpushed commits.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card