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.
Ideal for DevOps Agents requiring automated Github interactions and CI/CD pipeline management. Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Core Value
Empowers agents to automate tasks such as checking CI status, viewing workflow runs, and debugging failed steps using the gh CLI, facilitating seamless interaction with Github repositories and workflows via URLs or the --repo owner/repo syntax.
Ideal Agent Persona
Ideal for DevOps Agents requiring automated Github interactions and CI/CD pipeline management.
↓ Capabilities Granted for github
! Prerequisites & Limits
- Requires gh CLI installation and configuration
- Needs --repo owner/repo specification or URL when not in a git directory
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?
Ideal for DevOps Agents requiring automated Github interactions and CI/CD pipeline management. Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
How do I install github?
Run the command: npx killer-skills add rckim77/Daydream/github. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.
What are the use cases for github?
Key use cases include: Automating CI status checks on pull requests, Debugging failed workflow runs, Listing recent workflow runs for audit and monitoring purposes.
Which IDEs are compatible with github?
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?
Requires gh CLI installation and configuration. Needs --repo owner/repo specification or URL when not in a git directory.
↓ 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 rckim77/Daydream/github. 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 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
Install github, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.
