Orchestrate GitHub issues, PRs, and repository metadata via gh CLI, MCP, or REST API.
npx skills add https://github.com/ereferen/zellij-toolbox --skill github-ereferen
Please help me install this Agent Skill. Skill: github Source: https://github.com/ereferen/zellij-toolbox/tree/main/.claude/skills/github Command: npx skills add https://github.com/ereferen/zellij-toolbox --skill github-ereferen
GitHub operations such as creating issues, listing PRs, and reading repository metadata can be blocked by missing tooling or credentials. This Skill provides a robust, multi-step fallback strategy that automatically uses gh when available, MCP tools when gh is not present, and curl as a last resort to interact with the GitHub REST API.
List open issues in the current repository.
High-intent search queries and answers about installing and using this skill.
Automate GitHub operations by auto-detecting available tools and falling back to MCP tools or curl REST API calls when gh CLI is missing. This multi-step fallback ensures tasks like reading repository metadata continue executing across diverse environments.
Yes, you can access private repository issues and pull requests by authenticating with GITHUB_TOKEN. When the token is present, it securely handles authentication to fetch restricted resources; otherwise, it safely performs read-only requests for public data.
The best way to interact with the GitHub REST API in CI environments is using a robust fallback strategy that prioritizes gh CLI, then MCP tools, then curl. This enables seamless scripting and structured outputs suitable for automation workflows.
Yes, this approach works for both local development and CI automation workflows by providing flexible platform support. It authenticates with GITHUB_TOKEN when present and switches to read-only requests to guarantee robust command orchestration across environments.
GitHub API calls fail when tooling availability changes because single-method integrations lack fallback mechanisms. Using a prioritized fallback from gh CLI to MCP tools to curl REST API prevents these failures by auto-detecting available tools and adjusting execution paths.
No, you do not need credentials to list open issues in a public current repository. The system performs read-only requests automatically when GITHUB_TOKEN is absent, but you must provide the token to access private or restricted repository metadata.
jeffdtCreate, list, update, and close GitHub issues with labels and comments.
dongzhuoyaoFetch and manipulate GitHub pull requests, issues, releases, and repository metadata via authenticated CLI.
NourcineAbAutomate GitHub Actions workflow creation and optimization for CI/CD management.
prulloacCreate GitHub issue labels via MCP Server, GitHub CLI, or REST API.
