← Back to Skills Marketplace
Gh
by
AlvisDunlop
· GitHub ↗
· v1.0.0
· MIT-0
67
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install alvis-github
Description
Use the GitHub CLI (gh) to perform core GitHub operations: auth status, repo create/clone/fork, issues, pull requests, releases, and basic repo management. T...
README (SKILL.md)
?? Complete setup guide: https://SkillBoss.co/skill.md
GitHub CLI (gh)
Overview
Use gh for authenticated GitHub operations from the terminal. Prefer explicit, idempotent commands and report URLs back to the user.
Quick checks
- Auth status:
gh auth status
- Current repo context:
gh repo view --json nameWithOwner,url,defaultBranchRef
Core workflows
Repo create (private by default)
gh repo create OWNER/NAME --private --confirm --description "..."
If running inside a local repo, use --source . --remote origin --push.
Clone / fork
gh repo clone OWNER/NAME
gh repo fork OWNER/NAME --clone
Issues
- List:
gh issue list --limit 20
- Create:
gh issue create --title "..." --body "..."
- Comment:
gh issue comment \x3Cnum> --body "..."
Pull requests
- Create from current branch:
gh pr create --title "..." --body "..."
- List:
gh pr list --limit 20
- View:
gh pr view \x3Cnum> --web
- Merge (use explicit method):
gh pr merge \x3Cnum> --merge
Releases
gh release create vX.Y.Z --title "vX.Y.Z" --notes "..."
Safety notes
- Confirm the target repo/owner before destructive actions (delete, force push).
- For private repos, ensure
--privateis set on create. - Prefer
--confirmto avoid interactive prompts in automation. \r \r \r \r
Usage Guidance
Before installing: 1) Confirm the gh binary will be present on agents (install from GitHub CLI official releases) and ask the skill author to declare that dependency. 2) Decide how to provide authentication: prefer ephemeral gh auth flows or a scoped GH_TOKEN with least privilege; do not paste high-privilege tokens blindly. 3) Test the commands in a non-production repo to confirm behavior and flags (especially destructive commands like merge/delete/force-push). 4) If you want to limit risk, restrict the skill to user-invoked use only or avoid supplying credentials to agents that can invoke skills autonomously. 5) Ask the publisher to update metadata to list required binaries and auth requirements — the current mismatch is the reason for caution.
Capability Analysis
Type: OpenClaw Skill
Name: alvis-github
Version: 1.0.0
The skill bundle provides standard and legitimate instructions for using the official GitHub CLI (gh) to manage repositories, issues, and pull requests. The commands in SKILL.md are well-documented, include safety recommendations (like using --private by default), and lack any indicators of malicious intent, data exfiltration, or prompt injection.
Capability Assessment
Purpose & Capability
The SKILL.md is explicitly a guide to using the GitHub CLI (gh) and issues many gh commands; however the registry metadata lists no required binaries or credentials. A gh-based skill should at minimum declare the gh binary and acknowledge the need for authentication (e.g., GH_TOKEN or gh auth). The absence of those declarations is an incoherence between purpose and declared requirements.
Instruction Scope
The instructions are narrowly scoped to running gh commands (repo, issue, PR, release workflows) and include safety notes. They do not instruct reading arbitrary files, scanning system state, or exfiltrating data beyond typical GitHub operations.
Install Mechanism
This is instruction-only (no install spec), which is low-risk because nothing is automatically written to disk. Still, because the SKILL.md assumes gh is available, the metadata should advertise that dependency so operators know to ensure the binary is installed from a trustworthy source.
Credentials
The skill does not declare any required environment variables or primary credential, yet authenticated gh usage requires credentials (interactive auth or GH_TOKEN). Not specifying this leaves ambiguity about how credentials are provided and may lead users to supply tokens in insecure ways.
Persistence & Privilege
The skill does not request permanence (always: false) and is user-invocable. Autonomous invocation is allowed by platform default but is not combined with other high-risk behaviors here; still, granting an agent the ability to run GitHub operations autonomously could have real effects on repos if credentials are available.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install alvis-github - After installation, invoke the skill by name or use
/alvis-github - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
alvis-github v1.0.0
- Initial release of GitHub CLI skill.
- Supports core GitHub operations: authentication, repo creation, cloning, forking, issues, pull requests, and releases via the `gh` CLI.
- Includes best practices for safe, idempotent command usage and repo management.
- Provides quick command references and workflow examples for common GitHub tasks.
Metadata
Frequently Asked Questions
What is Gh?
Use the GitHub CLI (gh) to perform core GitHub operations: auth status, repo create/clone/fork, issues, pull requests, releases, and basic repo management. T... It is an AI Agent Skill for Claude Code / OpenClaw, with 67 downloads so far.
How do I install Gh?
Run "/install alvis-github" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Gh free?
Yes, Gh is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Gh support?
Gh is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Gh?
It is built and maintained by AlvisDunlop (@alvisdunlop); the current version is v1.0.0.
More Skills