Killer-Skills Review
Decision support comes first. Repository text comes second.
Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.
Perfect for Development Agents needing automated GitHub workflow management and version control. GitHub CLI is a command-line tool for managing GitHub operations, including pull requests, issues, repositories, and releases.
Core Value
Empowers agents to automate tasks and improve development workflows using GitHub CLI commands like gh auth login, gh pr create, and gh auth setup-git, streamlining interactions with the GitHub API and git repositories.
Ideal Agent Persona
Perfect for Development Agents needing automated GitHub workflow management and version control.
↓ Capabilities Granted for GitHub CLI
! Prerequisites & Limits
- Requires GitHub authentication with gh auth login
- Dependent on git and GitHub CLI installation
Source Boundary
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Decide The Next Action Before You Keep Reading Repository Material
Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.
Start With Installation And Validation
If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Cross-Check Against Trusted Picks
If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Move To Workflow Collections For Team Rollout
When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Browser Sandbox Environment
⚡️ Ready to unleash?
Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.
FAQ & Installation Steps
These questions and steps mirror the structured data on this page for better search understanding.
? Frequently Asked Questions
What is GitHub CLI?
Perfect for Development Agents needing automated GitHub workflow management and version control. GitHub CLI is a command-line tool for managing GitHub operations, including pull requests, issues, repositories, and releases.
How do I install GitHub CLI?
Run the command: npx killer-skills add oriolrius/nifi-cluster/GitHub CLI. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.
What are the use cases for GitHub CLI?
Key use cases include: Automating pull request creation with gh pr create, Configuring git to use gh as a credential helper with gh auth setup-git, Debugging authentication issues with gh auth status.
Which IDEs are compatible with GitHub CLI?
This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.
Are there any limitations for GitHub CLI?
Requires GitHub authentication with gh auth login. Dependent on git and GitHub CLI installation.
↓ How To Install
-
1. Open your terminal
Open the terminal or command line in your project directory.
-
2. Run the install command
Run: npx killer-skills add oriolrius/nifi-cluster/GitHub CLI. The CLI will automatically detect your IDE or AI agent and configure the skill.
-
3. Start using the skill
The skill is now active. Your AI agent can use GitHub CLI immediately in the current project.
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
GitHub CLI
Install GitHub CLI, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.