setup

Configure Azure MCP integration and resolve authentication failures during setup.

1.0k|91|Updated Jul 9, 2025
One-click install
npx skills add https://github.com/fcakyon/claude-codex-settings --skill setup-fcakyon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/github-dev/skills/setup
Command: npx skills add https://github.com/fcakyon/claude-codex-settings --skill setup-fcakyon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you configure the GitHub CLI (gh) and troubleshoot common authentication issues so you can run gh commands without interruptions.

Core Features & Use Cases

  • gh auth login setup: Initialize GitHub CLI authentication.
  • Status verification: Check authentication with gh auth status and gh api user --jq '.login'.
  • Troubleshooting: Resolve common issues like missing scopes or outdated gh.

Quick Start

Run gh auth login, then verify with gh auth status and gh api user --jq '.login' to confirm success.

Frequently Asked Questions about setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up GitHub CLI authentication?

GitHub CLI authentication is configured by running `gh auth login`, which prompts you to choose a protocol and authenticate with your GitHub account. Verify success with `gh auth status` and `gh api user --jq '.login'` to confirm your login is active.

What should I do if gh auth login fails or prompts repeatedly?

Authentication failures often stem from missing OAuth scopes, outdated gh installation, or credential conflicts. Run `gh auth status` to check current auth state, then `gh auth logout` followed by `gh auth login` to reinitialize. Ensure gh is updated to the latest version.

Can I use GitHub CLI without authenticating?

GitHub CLI works for public repositories without authentication, but most operations—including accessing private repos, creating issues, and using advanced APIs—require `gh auth login` to function without interruption.

How do I verify my GitHub CLI authentication is working?

Run `gh auth status` to display your current authentication state and logged-in user. Confirm successful authentication by executing `gh api user --jq '.login'`, which returns your GitHub username if credentials are valid.

What happens if I don't have the right GitHub permissions for gh commands?

Permission errors occur when your GitHub token lacks required OAuth scopes. Re-authenticate with `gh auth login` and grant all requested permissions during the interactive prompt. Verify scopes with `gh auth status --show-token` to see active permissions.