logo-generator

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.

Security Scan

The skill's runtime instructions are for the GitHub `gh` CLI, but the package is named and registered as a 'logo-generator' and fails to declare the `gh` dependency or the need for GitHub authentication — this mismatch is incoherent and should be investigated before use.

Purpose & Capability

The package name/metadata (logo-generator) does not match the SKILL.md, which documents a GitHub `gh` CLI integration. This mismatch suggests a packaging or metadata error (or possible misdirection).

Instruction Scope

The SKILL.md stays within a clear scope (running `gh` commands to inspect PRs, runs, and use `gh api`). It does not ask to read unrelated system files or exfiltrate data. However it assumes a local `gh` CLI and authenticated GitHub access without declaring that requirement.

Install Mechanism

Instruction-only skill with no install spec or code files; nothing is written to disk by the skill itself. Low install risk, but also means no provenance information is provided.

Credentials

The skill declares no required binaries or environment variables, but the runtime instructions require the `gh` CLI and an authenticated GitHub session (token stored by gh). The needed credential/access method is implicit and not documented, which is disproportionate to the declared requirements and obscures where credentials are used.

Persistence & Privilege

The skill does not request always:true and does not modify other skills or system-wide settings; autonomous invocation is allowed (default) but is not by itself a new concern here.

What to consider before installing

Do not install or enable this skill until the metadata mismatch is resolved. The SKILL.md clearly expects the GitHub `gh` CLI and an authenticated GitHub session, but the package is named 'logo-generator' and declares no dependencies or credential requirements. If you still want to use it: 1) verify the skill's source and author (origin is 'unknown'); 2) ensure `gh` is installed and you are comfortable with how it stores authentication (gh stores tokens locally/OS credential store); 3) test in a safe account or environment (no sensitive repos) to confirm behavior; 4) avoid supplying additional env vars or secrets to the skill — the SKILL.md does not ask for any but it will implicitly use your `gh` auth; and 5) ask the publisher to fix the name/metadata and explicitly document required binaries and authentication. The mismatch could be an innocent packaging mistake, but it could also indicate sloppy or malicious packaging, so treat it with caution.

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)"'