โ Back to Skills Marketplace
Github
by
Peter Steinberger
ยท GitHub โ
ยท v1.0.0
167124
Downloads
545
Stars
4117
Active Installs
1
Versions
Install in OpenClaw
/install github
Description
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.
README (SKILL.md)
GitHub Skill
Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.
Pull Requests
Check CI status on a PR:
gh pr checks 55 --repo owner/repo
List recent workflow runs:
gh run list --repo owner/repo --limit 10
View a run and see which steps failed:
gh run view \x3Crun-id> --repo owner/repo
View logs for failed steps only:
gh run view \x3Crun-id> --repo owner/repo --log-failed
API for Advanced Queries
The gh api command is useful for accessing data not available through other subcommands.
Get PR with specific fields:
gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'
JSON Output
Most commands support --json for structured output. You can use --jq to filter:
gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'
Usage Guidance
This skill is an examples-only guide for using the GitHub 'gh' CLI. Before installing or enabling it, make sure the agent environment actually has the 'gh' CLI installed and authenticated with a GitHub account or token. Be aware that any gh-authenticated credentials available to the agent determine what repositories/actions the skill can accessโlimit the token scope to the minimum necessary and only grant access to accounts/repos you trust. Because the skill runs shell-style gh commands, avoid enabling it in environments where you do not want automated commands to run against your GitHub resources.
Capability Analysis
Type: OpenClaw Skill
Name: github
Version: 1.0.0
The skill bundle provides instructions for interacting with GitHub using the `gh` CLI. All examples provided in `SKILL.md` demonstrate read-only operations (e.g., checking PR status, listing runs, viewing API data). While the `gh api` command itself offers broad capabilities that could be misused if the agent's GitHub token has extensive permissions, the skill's instructions and examples do not show any intent for malicious behavior, data exfiltration, prompt injection, or other high-risk actions. The content is clearly aligned with its stated purpose.
Capability Assessment
Purpose & Capability
The skill's name and description match the SKILL.md content: it instructs use of the GitHub 'gh' CLI (issues, PRs, runs, gh api). It does not ask for unrelated credentials or binaries.
Instruction Scope
All runtime instructions are specific gh CLI invocations (gh pr, gh run, gh api, gh issue). They remain within the stated purpose and do not direct the agent to read arbitrary local files, environment variables, or to transmit data to external endpoints outside GitHub.
Install Mechanism
There is no install spec and no code files. This is the lowest-risk model for an instruction-only skill.
Credentials
The skill declares no required env vars or credentials, which is reasonable for an instruction-only gh helper. However, effective use requires the 'gh' CLI to be installed and authenticated in the agent environment (e.g., gh auth login or GITHUB_TOKEN); the SKILL.md does not mention authentication or token scope, so users should ensure their gh credentials are present and appropriately scoped.
Persistence & Privilege
always is false and there is no install step or self-modifying behavior. The skill does not request persistent presence or elevated system privileges.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install github - After installation, invoke the skill by name or use
/github - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Metadata
More Skills