Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

GitHub Issues Management · nousresearch | DecimalAI

nousresearch/github-issues

NewSkillScoreMaintained

Create, triage, label, assign GitHub issues via gh or REST.

productivityby nousresearch

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Project Management pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/nousresearch-github-issues/SKILL.md

decimalai skills pull nousresearch-github-issues --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/nousresearch-github-issues/SKILL.md https://app.decimal.ai/s/nousresearch-github-issues/SKILL.md

Raw file: /s/nousresearch-github-issues/SKILL.md ↗ · machine-readable summary at /s/nousresearch-github-issues.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 19d ago

—+262% tokens0% turns73% of whole cases pass with skill (16/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-08	✗→✓	▲ Improved	275%	0%
case-15	✗→✓	▲ Improved	360%	0%
case-07	✓→✗	▼ Worse	578%	0%
case-10	✓→✗	▼ Worse	301%	0%
case-05	✓→✓	＝ Same ✓	181%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 8/17/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

nousresearch / hermes-agent

skills/github/github-issues/SKILL.md

View on GitHub ↗

License MITImported 8/17/2026Version v2Bundled 2 files

Skill contents

templates/

SKILL.md

GitHub Issues Management

Create, search, triage, and manage GitHub issues. Each section shows gh first, then the curl fallback.

Prerequisites

Authenticated with GitHub (see github-auth skill)
Inside a git repo with a GitHub remote, or specify the repo explicitly

Setup

bash
if command -v gh &>/dev/null && gh auth status &>/dev/null; then
  AUTH="gh"
else
  AUTH="git"
  if [ -z "$GITHUB_TOKEN" ]; then
    if _hermes_env="${HERMES_HOME:-$HOME/.hermes}/.env"; [ -f "$_hermes_env" ] && grep -q "^GITHUB_TOKEN=" "$_hermes_env"; then
      GITHUB_TOKEN=$(grep "^GITHUB_TOKEN=" "$_hermes_env" | head -1 | cut -d= -f2 | tr -d '\n\r')
    elif grep -q "github.com" ~/.git-credentials 2>/dev/null; then
      GITHUB_TOKEN=$(uv run python "${HERMES_HOME:-$HOME/.hermes}/skills/github/github-auth/scripts/git-credential-token.py")
    fi
  fi
fi

REMOTE_URL=$(git remote get-url origin)
OWNER_REPO=$(echo "$REMOTE_URL" | sed -E 's|.*github\.com[:/]||; s|\.git$||')
OWNER=$(echo "$OWNER_REPO" | cut -d/ -f1)
REPO=$(echo "$OWNER_REPO" | cut -d/ -f2)

1. Viewing Issues

With gh:

bash
gh issue list
gh issue list --state open --label "bug"
gh issue list --assignee @me
gh issue list --search "authentication error" --state all
gh issue view 42

With curl:

bash
# List open issues
curl -s \
  -H "Authorization: token $GITHUB_TOKEN" \
  "https://api.github.com/repos/$OWNER/$REPO/issues?state=open&per_page=20" \
  | python -c "
import sys, json
for i in json.load(sys.stdin):
    if 'pull_request' not in i:  # GitHub API returns PRs in /issues too
        labels = ', '.join(l['name'] for l in i['labels'])
        print(f\"#{i['number']:5}  {i['state']:6}  {labels:30}  {i['title']}\")"

# Filter by label
curl -s \
  -H "Authorization: token $GITHUB_TOKEN" \
  "https://api.github.com/repos/$OWNER/$REPO/issues?state=open&labels=bug&per_page=20" \
  | python -c "
import sys, json
for i in json.load(sys.stdin):
    if 'pull_request' not in i:
        print(f\"#{i['number']}  {i['title']}\")"

# View a specific issue
curl -s \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/issues/42 \
  | python -c "
import sys, json
i = json.load(sys.stdin)
labels = ', '.join(l['name'] for l in i['labels'])
assignees = ', '.join(a['login'] for a in i['assignees'])
print(f\"#{i['number']}: {i['title']}\")
print(f\"State: {i['state']}  Labels: {labels}  Assignees: {assignees}\")
print(f\"Author: {i['user']['login']}  Created: {i['created_at']}\")
print(f\"\n{i['body']}\")"

# Search issues
curl -s \
  -H "Authorization: token $GITHUB_TOKEN" \
  "https://api.github.com/search/issues?q=authentication+error+repo:$OWNER/$REPO" \
  | python -c "
import sys, json
for i in json.load(sys.stdin)['items']:
    print(f\"#{i['number']}  {i['state']:6}  {i['title']}\")"

2. Creating Issues

With gh:

bash
gh issue create \
  --title "Login redirect ignores ?next= parameter" \
  --body "## Description
After logging in, users always land on /dashboard.

## Steps to Reproduce
1. Navigate to /settings while logged out
2. Get redirected to /login?next=/settings
3. Log in
4. Actual: redirected to /dashboard (should go to /settings)

## Expected Behavior
Respect the ?next= query parameter." \
  --label "bug,backend" \
  --assignee "username"

With curl:

bash
curl -s -X POST \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/issues \
  -d '{
    "title": "Login redirect ignores ?next= parameter",
    "body": "## Description\nAfter logging in, users always land on /dashboard.\n\n## Steps to Reproduce\n1. Navigate to /settings while logged out\n2. Get redirected to /login?next=/settings\n3. Log in\n4. Actual: redirected to /dashboard\n\n## Expected Behavior\nRespect the ?next= query parameter.",
    "labels": ["bug", "backend"],
    "assignees": ["username"]
  }'

Bug Report Template

## Bug Description
<What's happening>

## Steps to Reproduce
1. <step>
2. <step>

## Expected Behavior
<What should happen>

## Actual Behavior
<What actually happens>

## Environment
- OS: <os>
- Version: <version>

Feature Request Template

## Feature Description
<What you want>

## Motivation
<Why this would be useful>

## Proposed Solution
<How it could work>

## Alternatives Considered
<Other approaches>

3. Managing Issues

Add/Remove Labels

With gh:

bash
gh issue edit 42 --add-label "priority:high,bug"
gh issue edit 42 --remove-label "needs-triage"

With curl:

bash
# Add labels
curl -s -X POST \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/issues/42/labels \
  -d '{"labels": ["priority:high", "bug"]}'

# Remove a label
curl -s -X DELETE \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/issues/42/labels/needs-triage

# List available labels in the repo
curl -s \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/labels \
  | python -c "
import sys, json
for l in json.load(sys.stdin):
    print(f\"  {l['name']:30}  {l.get('description', '')}\")"

Assignment

With gh:

bash
gh issue edit 42 --add-assignee username
gh issue edit 42 --add-assignee @me

With curl:

bash
curl -s -X POST \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/issues/42/assignees \
  -d '{"assignees": ["username"]}'

Commenting

With gh:

bash
gh issue comment 42 --body "Investigated — root cause is in auth middleware. Working on a fix."

With curl:

bash
curl -s -X POST \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/issues/42/comments \
  -d '{"body": "Investigated — root cause is in auth middleware. Working on a fix."}'

Closing and Reopening

With gh:

bash
gh issue close 42
gh issue close 42 --reason "not planned"
gh issue reopen 42

With curl:

bash
# Close
curl -s -X PATCH \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/issues/42 \
  -d '{"state": "closed", "state_reason": "completed"}'

# Reopen
curl -s -X PATCH \
  -H "Authorization: token $GITHUB_TOKEN" \
  https://api.github.com/repos/$OWNER/$REPO/issues/42 \
  -d '{"state": "open"}'

Linking Issues to PRs

Issues are automatically closed when a PR merges with the right keywords in the body:

Closes #42
Fixes #42
Resolves #42

To create a branch from an issue:

With gh:

bash
gh issue develop 42 --checkout

With git (manual equivalent):

bash
git checkout main && git pull origin main
git checkout -b fix/issue-42-login-redirect

4. Issue Triage Workflow

When asked to triage issues:

List untriaged issues:

bash
# With gh
gh issue list --label "needs-triage" --state open

# With curl
curl -s \
  -H "Authorization: token $GITHUB_TOKEN" \
  "https://api.github.com/repos/$OWNER/$REPO/issues?labels=needs-triage&state=open" \
  | python -c "
import sys, json
for i in json.load(sys.stdin):
    if 'pull_request' not in i:
        print(f\"#{i['number']}  {i['title']}\")"

Read and categorize each issue (view details, understand the bug/feature)

Apply labels and priority (see Managing Issues above)

Assign if the owner is clear

Comment with triage notes if needed

5. Bulk Operations

For batch operations, combine API calls with shell scripting:

With gh:

bash
# Close all issues with a specific label
gh issue list --label "wontfix" --json number --jq '.[].number' | \
  xargs -I {} gh issue close {} --reason "not planned"

With curl:

bash
# List issue numbers with a label, then close each
curl -s \
  -H "Authorization: token $GITHUB_TOKEN" \
  "https://api.github.com/repos/$OWNER/$REPO/issues?labels=wontfix&state=open" \
  | python -c "import sys,json; [print(i['number']) for i in json.load(sys.stdin)]" \
  | while read num; do
    curl -s -X PATCH \
      -H "Authorization: token $GITHUB_TOKEN" \
      https://api.github.com/repos/$OWNER/$REPO/issues/$num \
      -d '{"state": "closed", "state_reason": "not_planned"}'
    echo "Closed #$num"
  done

Quick Reference Table

| Action | gh | curl endpoint | |--------|-----|--------------| | List issues | gh issue list | GET /repos/{o}/{r}/issues | | View issue | gh issue view N | GET /repos/{o}/{r}/issues/N | | Create issue | gh issue create ... | POST /repos/{o}/{r}/issues | | Add labels | gh issue edit N --add-label ... | POST /repos/{o}/{r}/issues/N/labels | | Assign | gh issue edit N --add-assignee ... | POST /repos/{o}/{r}/issues/N/assignees | | Comment | gh issue comment N --body ... | POST /repos/{o}/{r}/issues/N/comments | | Close | gh issue close N | PATCH /repos/{o}/{r}/issues/N | | Search | gh issue list --search "..." | GET /search/issues?q=... |

Want to see if nousresearch/github-issues would activate on your phrasing? Try it before you install — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/17/2026, 03:25 UTC · 22 cases

Measured on 19 comparable cases — below the 22 needed to publish a lift, so this result is shown here but not on the registry card or leaderboard.

Lift

0%

73% vs 73%

Agent turns

0%

1.0 vs 1.0

Tokens

+262%

3,722.74 vs 1,029.11

fail → pass · 2pass → pass · 14fail → fail · 4pass → fail · 2

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-03 Please update our repository's GitHub Actions secrets to add a new `DATABASE_URL` secret using the command line.	fail→fail	5,421	9,752	+80%	1	1	0%	1,027	4,998	+387%	0	0	—
case-04 Configure branch protection rules on `main` to enforce pull request approvals and status checks.	fail→fail	7,297	13,070	+79%	1	1	0%	1,460	5,379	+268%	0	0	—
case-01 Our repository has several newly submitted tickets waiting to be reviewed. Please execute our standard issue triage workflow on open items that require triage, categorizing them with appropriate tags and priorities, assigning an owner if obvious, and adding a triage summary note.	fail→fail	4,637	4,071	-12%	1	1	0%	222	3,215	+1348%	0	0	—
case-02 We need to create a new Pull Request against `main` for our feature branch `feat/auth-login` with a description and reviewers requested via CLI or curl API.	fail→fail	8,791	7,568	-14%	1	1	0%	1,982	4,741	+139%	0	0	—
case-05 Show me all open GitHub issues assigned to my account using the command line tool.	pass→pass	6,806	3,508	-48%	1	1	0%	1,290	3,621	+181%	0	0	—
case-06 We are building a curl script to fetch open issues from REST API `https://api.github.com/repos/acme/widgets/issues?state=open`. Since GitHub's REST issues endpoint includes pull requests, show how to filter out pull requests in Python.	pass→pass	6,427	4,539	-29%	1	1	0%	1,398	3,937	+182%	0	0	—
case-07 Search for all issues containing 'authentication error' in the current repository regardless of whether they are open or closed.	pass→fail	2,961	7,056	+138%	1	1	0%	553	3,748	+578%	0	0	—
case-08 Create a bug report issue titled 'Navigation menu fails on mobile web' assigned to user 'johndoe' with labels 'bug' and 'backend' and a description body.	fail→pass	4,713	2,272	-52%	1	1	0%	905	3,391	+275%	0	0	—
case-09 Write a cURL POST request to create an issue in repo `acme/app` setting title, body, labels, and assignees.	pass→pass	4,262	2,797	-34%	1	1	0%	944	3,580	+279%	0	0	—
case-10 Update issue #42 by adding labels 'priority:high' and 'bug', while removing the label 'needs-triage'.	pass→fail	4,589	5,315	+16%	1	1	0%	793	3,180	+301%	0	0	—
case-11 Write a cURL command to add labels 'priority:high' and 'bug' to issue #42 using the GitHub REST API.	pass→pass	4,814	2,326	-52%	1	1	0%	1,107	3,440	+211%	0	0	—
case-12 Construct a cURL command to remove the label 'needs-triage' from issue #42.	pass→pass	3,519	2,274	-35%	1	1	0%	685	3,411	+398%	0	0	—
case-13 Assign issue #42 to myself using the GitHub CLI command.	pass→pass	1,953	1,131	-42%	1	1	0%	287	3,128	+990%	0	0	—
case-14 Add a comment to issue #42 stating 'Identified race condition in cache refresh' using the CLI.	pass→pass	1,775	1,360	-23%	1	1	0%	330	3,173	+862%	0	0	—
case-15 Close issue #42 and indicate that it was closed because it is not planned.	fail→pass	4,206	2,941	-30%	1	1	0%	776	3,568	+360%	0	0	—
case-16 Write a cURL request to close issue #42 via REST API indicating it was not planned.	pass→pass	4,119	2,329	-43%	1	1	0%	901	3,411	+279%	0	0	—
case-17 How do you reopen issue #42 using cURL with the REST API?	pass→pass	6,748	2,128	-68%	1	1	0%	1,464	3,418	+133%	0	0	—
case-18 Create a local git branch directly linked to issue #42 and check it out using the GitHub CLI.	pass→pass	3,945	1,929	-51%	1	1	0%	739	3,297	+346%	0	0	—
case-19 Write a command pipeline to close all open issues labeled 'wontfix' using gh CLI and jq.	pass→pass	7,949	3,590	-55%	1	1	0%	1,609	3,625	+125%	0	0	—
case-20 Write a bash shell loop that uses cURL to fetch all issue numbers labeled 'wontfix' and PATCHes each to close it with reason 'not_planned'.	pass→pass	6,651	4,509	-32%	1	1	0%	1,522	3,943	+159%	0	0	—
case-21 View the detailed description and metadata of issue #42 using the GitHub CLI.	pass→pass	2,224	910	-59%	1	1	0%	366	3,086	+743%	0	0	—
case-22 Write a cURL command to fetch all available labels defined in the repository `acme/app`.	pass→pass	4,023	2,815	-30%	1	1	0%	761	3,585	+371%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 19 counted toward the lift figure. The other 3 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of 0 percentage points is the difference between those two pass rates over the 19 comparable cases. 2 cases got worse with the skill loaded, and they are included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 72.7%
Pass rate with the skill: 72.7%
Cases attempted: 22
Cases counted toward lift: 19
Cases that regressed: 2
Skill version measured: v2
Run completed: 8/17/2026, 03:25 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-08

Prompt

Create a bug report issue titled 'Navigation menu fails on mobile web' assigned to user 'johndoe' with labels 'bug' and 'backend' and a description body.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signalsno signals yet

BenchmarkRun a verified benchmark with positive lift

Live evalNeeds ≥20 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+263% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

No signals yet — run a benchmark or collect evaluated traces to earn a score.

Verified on gemini-3.6-flash · re-tested 19 days ago

Model	Method	Date	Lift
gemini-3.6-flash	verified	8/8/2026	+14%

Other measured skills in the registry, with their headline benchmark lift.