Lovefromio 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· 43·1 current·1 all-time

byAI@lovefromio

OpenClaw Prompt Flow

Install with OpenClaw

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

Previewing Install & Setup.

Prompt PreviewInstall & Setup

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install lovefromio-github

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

The name/description match the SKILL.md instructions which instruct use of the `gh` CLI (issues, PRs, runs, and gh api). The skill does not request unrelated binaries, credentials, or config paths. Note: it implicitly assumes the `gh` CLI and GitHub authentication are present on the host, but does not declare or require any credentials itself.

✓

Instruction Scope

All runtime instructions are limited to `gh` commands and GitHub API endpoints (repo paths, PR numbers, run IDs). The instructions do not reference system files, external endpoints, or environment variables beyond what `gh` normally uses. Using `gh api` can access arbitrary GitHub API data, which is expected for this skill.

✓

Install Mechanism

There is no install spec and no code files to write to disk (instruction-only). This is the lowest-risk install model.

ℹ

Credentials

The skill declares no required environment variables or credentials. In practice it will rely on whatever GitHub authentication the `gh` CLI is configured with (e.g., an existing gh auth session or GITHUB_TOKEN). That is proportionate, but users should be aware the agent will run `gh` with whatever credentials are present.

✓

Persistence & Privilege

always is false and the skill is user-invocable. There is no indication it modifies other skills or system configuration; it does not request permanent presence or elevated privileges.

Assessment

This skill is a thin wrapper around the existing GitHub CLI and appears coherent. Before installing, verify you trust the agent to run `gh` commands with your GitHub credentials: ensure `gh` is installed and authenticated with a least-privilege token (or an account with limited repo access). Because the skill source/homepage is not provided, if you need stronger provenance guarantees test it in a sandbox or request the author/source before granting it access to sensitive repositories or org-level tokens.

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

latestvk9794fa5egsmz853mddpj5ke9s85m61r

43downloads

0stars

1versions

Updated 1d 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...