Github issue create

Skill MauricioPerera/agent-skills-pack/skills/github-issue-create

A curated pack of 7 practical agent-skills demonstrating real-world patterns: HTTP, GitHub CLI, ripgrep, file ops, JSON processing, encoding. Each SKILL.md validated against the v0.1 spec.

Install

npx -y skills add MauricioPerera/agent-skills-pack --skill github-issue-create

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Creates a new GitHub issue in a specified repository. v2 ships a pack-distributed CustomCommand (command.js) that calls the GitHub REST API directly — no host gh CLI required. Authentication via $GH_TOKEN; the agent never sees the credential.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.9 KB, as published. Nobody here has run it

Create a GitHub issue

Creates a new GitHub issue using the GitHub CLI (gh).

Privacy invariant — credential isolation

This skill demonstrates the SPEC §8 P1 invariant in its strongest form:

The command_template does NOT reference $GH_TOKEN or any credential variable explicitly.
gh itself reads credentials from:
1. The environment variable $GH_TOKEN (or $GITHUB_TOKEN), OR
2. Its own keyring config at ~/.config/gh/hosts.yml.
Whichever source gh finds, the credential never appears in the resolved command.
The agent emits gh issue create --repo X --title Y --body Z — no token, no auth header, no secret.
The shell hands the literal command to gh, which performs auth internally.

This is stronger than the explicit-$VAR pattern (e.g., --header 'Bearer $TOKEN'): even the variable name doesn't appear in the resolved command. The skill is completely credential-agnostic at the LLM-context level.

Setup (operator-side, before the agent runs)

# Option A: keychain-backed (recommended)
gh auth login

# Option B: env-based (for CI, ephemeral shells)
export GH_TOKEN=ghp_your_token_here

If neither is configured, the skill exits with gh: error: authentication required — a clear signal to the agent that credentials are missing, without leaking what credentials would look like.

Output

stdout: a URL to the newly-created issue, like https://github.com/owner/repo/issues/123.
stderr: gh progress messages or auth errors.
exit code: 0 on success; 1 on auth failure or API error.

Caveats

The gh CLI must be installed (declared in required_commands). On CI, gh is preinstalled on GitHub Actions runners; on local dev, install via brew install gh / apt install gh / etc.
The repository must exist and the authenticated user must have issue creation permission. For org repos, this typically means the user is a member or has been invited.
This skill creates an issue with no labels, assignees, or milestones. To add those, use --label, --assignee, --milestone flags directly or extend this skill.
The body arg supports full GitHub-flavored markdown including code fences, tables, mentions (@username), and issue/PR references (#123).