Gh

v2.0.0

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...

0· 90·0 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for alvisdunlop/alvis-gh-v2.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Gh" (alvisdunlop/alvis-gh-v2) from ClawHub.
Skill page: https://clawhub.ai/alvisdunlop/alvis-gh-v2
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install alvis-gh-v2

ClawHub CLI

Package manager switcher

npx clawhub@latest install alvis-gh-v2
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The SKILL.md is a straightforward guide to running the GitHub CLI (gh) and the name/description match the instructions. One mismatch: the skill metadata lists no required binaries, but the runtime instructions assume the gh binary is available on PATH. This is a documentation omission rather than a functional inconsistency.
Instruction Scope
Instructions only show gh commands (auth status, repo create/clone/fork, issues, PRs, releases). They reference operating inside a local repo (e.g., --source .) which is appropriate for the task. Several commands are destructive (merge, delete/force push mentioned in safety notes); the SKILL.md does advise confirming targets and using --confirm to avoid interactive prompts.
Install Mechanism
No install spec or code files are provided; this is instruction-only so nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables or credentials. It implicitly relies on whatever GitHub authentication the user's gh CLI has configured (gh auth). This is proportionate, but users should be aware the agent will run commands using their existing gh credentials if the agent is allowed to execute.
Persistence & Privilege
always is false and the skill does not request persistent/system-wide changes or access to other skills' configs. Autonomous invocation is allowed (platform default) but not combined with any broad privileges here.
Assessment
This skill is an on-device guide for using the GitHub CLI (gh). Before installing: ensure you have gh installed and authenticated (gh auth login) because the SKILL.md assumes the binary exists but the metadata doesn't list it. Only allow the agent to run this skill if you trust it to execute GitHub write/destructive commands (create repos, merge PRs, force-push, delete); review commands before execution. Note the SKILL.md links to an external setup guide (https://SkillBoss.co/skill.md) — treat that link like any external resource and verify it if you follow it.

Like a lobster shell, security has layers — review code before you run it.

latestvk974v335td3a18n9p5z4k98pw184zq40
90downloads
0stars
2versions
Updated 1w ago
v2.0.0
MIT-0

?? 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 <num> --body "..."

Pull requests

  • Create from current branch:
gh pr create --title "..." --body "..."
  • List:
gh pr list --limit 20
  • View:
gh pr view <num> --web
  • Merge (use explicit method):
gh pr merge <num> --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 --private is set on create.
  • Prefer --confirm to avoid interactive prompts in automation.

Comments

Loading comments...