Check for and install GitHub CLI to prepare a development environment.
This is an open-source, prompt-only installation skill that mainly documents how to install and configure GitHub CLI, without embedded executable logic by itself. Overall risk is low, but the material explicitly includes local install commands, sudo elevation, and subsequent GitHub authentication/token scope changes, so local execution and credential scope should be reviewed carefully.
The skill itself declares no required secrets, but the README explicitly instructs users to run `gh auth login` and optionally `gh auth refresh -s notifications`, which expands the GitHub token scope to notifications. This is a normal authorization step for the stated purpose, but users should avoid granting broader scopes than necessary.
The documented installation flow connects to GitHub-related endpoints such as `cli.github.com` to fetch packages and keyrings, and `gh auth login` also communicates with GitHub services. There is no indication of data exfiltration to unknown or unrelated third-party endpoints, but the installation and authentication steps do involve expected network access.
The README provides local shell/package-manager commands such as `brew install`, `winget install`, and a Linux install command using `sudo apt`, writing APT keyrings, and adding source lists, which involve local process execution and system-level installation changes. This is inherent to installer-type tooling, and no extra execution beyond the stated purpose is evident.
The documentation involves modifying system installation/configuration locations such as `/etc/apt/keyrings/` and `/etc/apt/sources.list.d/`, as well as local GitHub CLI configuration changes via `gh config set pager cat`; after login, gh may also store local authentication state. There is no stated bulk reading or export of user files, but it does access system configuration paths and local CLI credential/config storage.
System checks indicate this is prompt-only and open-source, sourced from the GitHub repository `microsoft/vscode-team-kit`, making the contents auditable. There is no sign of a closed-source binary bundle or hidden remote dependency behavior. Although the repo has 0 stars and unclear license/maintenance status, the supply-chain risk is still relatively low because the content is simple and open for inspection.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "inbox-install-gh-cli" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/vscode-team-kit/main/github-inbox/skills/inbox-install-gh-cli/SKILL.md 2. Save it as ~/.claude/skills/inbox-install-gh-cli/SKILL.md 3. Reload skills and tell me it's ready
Please check whether GitHub CLI (gh) is installed on my computer; if not, install it for my current operating system and tell me how to verify the installation.
Returns the installation status, setup steps or results, and commands to verify that gh works.
I’m about to run an automation script that depends on gh. First make sure GitHub CLI is installed, and explain how to handle PATH or permission issues.
Ensures gh is ready to use and provides guidance for common environment configuration issues.
I’m a beginner. Help me install GitHub CLI, then show the basic steps to log in to GitHub and test that commands work.
Provides installation results plus follow-up guidance for gh auth login and basic test commands.
Before using any gh commands, check if gh is installed by running:
gh --version
If gh is not found, install it based on the operating system:
brew install gh
(type -p wget >/dev/null || (sudo apt update && sudo apt-get install wget -y)) && sudo mkdir -p -m 755 /etc/apt/keyrings && out=$(mktemp) && wget -nv -O$out https://cli.github.com/packages/githubcli-archive-keyring.gpg && cat $out | sudo tee /etc/apt/keyrings/githubcli-archive-keyring.gpg > /dev/null && sudo chmod go+r /etc/apt/keyrings/githubcli-archive-keyring.gpg && echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null && sudo apt update && sudo apt install gh -y
winget install --id GitHub.cli
Authenticate with GitHub:
gh auth login
If the user needs notifications access, ensure the token has the notifications scope:
gh auth refresh -s notifications
Disable the pager to prevent terminal buffer issues:
gh config set pager cat
Set up Component Explorer with CLI, MCP, and VS Code tooling.
Add emoji reactions to GitHub issues or pull requests quickly.
Let AI agents read and write memory with environment-aware storage fallback.
Gather independent multi-model plans and debates for implementation and architecture decisions.
Get high-signal second opinions on plans, designs, and implementations early.
Fetch and review GitHub notifications quickly using the gh CLI.
Manage issues, PRs, logs, releases, and repos with GitHub CLI.
Manage end-to-end GitHub workflows safely through verified git and gh steps.
Address review and issue comments on the current branch's GitHub PR with gh CLI.
Execute and explore GitHub actions through wrapped gh CLI commands in AI.
Run Git and GitHub CLI outside sandbox restrictions for smoother repository operations.
Open GitHub notification links in a browser for quick review.