Aj Github

v1.0.0

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.

⭐ 0· 157·0 current·0 all-time

by@aceundefeated·fork of @steipete/github (1.0.0)

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for aceundefeated/aj-github.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Aj Github" (aceundefeated/aj-github) from ClawHub.
Skill page: https://clawhub.ai/aceundefeated/aj-github
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 aj-github

ClawHub CLI

Package manager switcher

npx clawhub@latest install aj-github

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

Name/description match the instructions: all examples use the gh CLI (pr, run, issue, api). The skill does not request unrelated binaries, credentials, or config paths.

✓

Instruction Scope

SKILL.md only shows gh commands and guidance to use --repo or URLs. It does not instruct reading arbitrary files, contacting unexpected endpoints, or accessing unrelated environment variables.

✓

Install Mechanism

No install spec and no code files — instruction-only. Nothing is downloaded or written to disk by the skill itself.

✓

Credentials

The skill declares no required environment variables or credentials. Using gh will rely on whatever GitHub auth the local environment already provides (normal and expected).

✓

Persistence & Privilege

always is false and the skill does not request persistent system privileges or modify other skills' configs. It is user-invokable and may be called autonomously per platform defaults.

Assessment

This skill is just documentation for the gh CLI. Before installing/using it: (1) ensure the gh CLI is installed and you're comfortable with the agent having access to your gh authentication (the CLI will use your existing gh auth or GH_TOKEN), because commands run by the agent can act with your GitHub permissions; (2) prefer to require explicit confirmation before running destructive commands (merge, close, delete); (3) note a minor metadata inconsistency: _meta.json contains a different ownerId/slug than the registry listing — likely benign but worth double-checking if provenance matters.

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

latestvk977axqqh85xgt349e3yty2cfn83n3cg

157downloads

0stars

1versions

Updated 1mo ago

v1.0.0

MIT-0

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 <run-id> --repo owner/repo

View logs for failed steps only:

gh run view <run-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)"'

Comments

Loading comments...