Authenticate with GitHub using stored credentials for API and git commands.
npx skills add https://github.com/jackspace/ClaudeSkillz --skill github-auth
Please help me install this Agent Skill. Skill: github-auth Source: https://github.com/jackspace/ClaudeSkillz/tree/main/skills/github-auth Command: npx skills add https://github.com/jackspace/ClaudeSkillz --skill github-auth
This Skill provides best-practice patterns for securely handling GitHub credentials (PATs, SSH keys) and performing authenticated GitHub operations.
Use a local .env file or CI secrets to supply credentials, then follow the examples to authenticate with gh and perform common operations without exposing secrets in code.
High-intent search queries and answers about installing and using this skill.
Securely authenticate with GitHub by storing credentials in a .env file and using either GitHub CLI (gh) with a Personal Access Token (PAT) or SSH keys for git operations. This approach keeps credentials out of code and URLs while supporting both API calls and repository management.
Store GitHub credentials as CI/CD secrets rather than hardcoding them. Use PATs for API operations and SSH keys for git commands. This practice prevents credential leakage, enforces secret management, and enables safe automation for repository operations like PRs, issues, and releases.
Yes, SSH-based Git operations are a secure alternative to PATs for repository management. SSH keys avoid storing tokens in environment files and provide an additional authentication method suitable for local development and automation scripts.
Load credentials from a .env file or CI secrets manager instead of embedding them in code or URLs. Follow security practices that protect the environment file, rotate tokens regularly, and use authenticated methods (gh CLI or direct API calls with PATs) that keep credentials separate from your codebase.
Yes, GitHub CLI supports authentication using stored PATs from a .env file or secrets manager. This enables safe, authenticated API operations and git commands in local development, automation scripts, and CI/CD pipelines without exposing credentials.
Rotate tokens regularly as part of credential management best practices. Store new tokens in .env files or CI secrets, update authenticated scripts and workflows, and revoke old tokens to maintain security across local development, automation, and CI/CD environments.
CyapstayeConfigures GitHub authentication via gh CLI, SSH keys, or tokens.
kangju2000Manage GitHub pull requests, issues, workflows, releases, and repositories via the gh CLI.
blueskies1818Configure GitHub authentication using HTTPS tokens, SSH keys, or gh CLI.
vince-winkintelManage GitLab SSH keys via the glab CLI.
