How do I install the Githubissues skill?

Run npx skillmds@latest add tomevault-io/githubissues in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Githubissues safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Githubissues?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Githubissues free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Githubissues?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Githubissues by tomevault-io — Agent Skill

Name: Githubissues
Author: tomevault-io

File contents

Issue Triage

Analyze open issues to identify priority, stale items, and cleanup candidates.

When to Use

Weekly issue grooming
Before sprint planning
When backlog grows too large

Auto-approved: All gh commands are read-only and auto-approved.

Analysis Steps

1. All Open Issues

gh issue list --repo kagenti/kagenti --state open --limit 100 --json number,title,labels,createdAt,updatedAt,assignees,comments

2. Issues Without Attention (no assignee, no comments)

gh issue list --repo kagenti/kagenti --state open --limit 100 --json number,title,assignees,comments --jq '.[] | select(.assignees | length == 0) | select(.comments == 0) | "#\(.number) \(.title)"'

3. Stale Issues (no update > 30 days)

gh issue list --repo kagenti/kagenti --state open --limit 100 --json number,title,updatedAt --jq '.[] | select(.updatedAt < (now - 30*24*3600 | strftime("%Y-%m-%dT%H:%M:%SZ"))) | "#\(.number) \(.title) (last: \(.updatedAt))"'

4. Blocking / High Priority

gh issue list --repo kagenti/kagenti --state open --label "priority/critical,priority/high,blocking" --json number,title,labels

5. Security Issues

gh issue list --repo kagenti/kagenti --state open --label "security" --json number,title,createdAt

Triage Report

## Issue Triage Report

### Needs Attention (no assignee, no comments): N
- [list]

### Stale (> 30 days no activity): N
- [list — consider closing or updating]

### Blocking / High Priority: N
- [list — needs immediate action]

### Candidates to Close
- [issues that are resolved, outdated, or duplicated]

Optionally Close or Comment

gh issue close <number> --repo kagenti/kagenti --comment "Closing as resolved/outdated. See #<newer-issue> for updated version."

Related Skills

github:last-week - Weekly summary including issues
github:prs - PR health analysis
repo:issue - Create properly formatted issues

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: githubissuesdescription: Issue triage - stale issues, blocking, no attention, should-close analysis Use when this capability is needed.---# Issue TriageAnalyze open issues to identify priority, stale items, and cleanup candidates.## When to Use- Weekly issue grooming- Before sprint planning- When backlog grows too large> **Auto-approved**: All `gh` commands are read-only and auto-approved.## Analysis Steps### 1. All Open Issues```bashgh issue list --repo kagenti/kagenti --state open --limit 100 --json number,title,labels,createdAt,updatedAt,assignees,comments```### 2. Issues Without Attention (no assignee, no comments)```bashgh issue list --repo kagenti/kagenti --state open --limit 100 --json number,title,assignees,comments --jq '.[] | select(.assignees | length == 0) | select(.comments == 0) | "#\(.number) \(.title)"'```### 3. Stale Issues (no update > 30 days)```bashgh issue list --repo kagenti/kagenti --state open --limit 100 --json number,title,updatedAt --jq '.[] | select(.updatedAt < (now - 30*24*3600 | strftime("%Y-%m-%dT%H:%M:%SZ"))) | "#\(.number) \(.title) (last: \(.updatedAt))"'```### 4. Blocking / High Priority```bashgh issue list --repo kagenti/kagenti --state open --label "priority/critical,priority/high,blocking" --json number,title,labels```### 5. Security Issues```bashgh issue list --repo kagenti/kagenti --state open --label "security" --json number,title,createdAt```## Triage Report```markdown## Issue Triage Report### Needs Attention (no assignee, no comments): N- [list]### Stale (> 30 days no activity): N- [list — consider closing or updating]### Blocking / High Priority: N- [list — needs immediate action]### Candidates to Close- [issues that are resolved, outdated, or duplicated]```### Optionally Close or Comment```bashgh issue close <number> --repo kagenti/kagenti --comment "Closing as resolved/outdated. See #<newer-issue> for updated version."```## Related Skills- `github:last-week` - Weekly summary including issues- `github:prs` - PR health analysis- `repo:issue` - Create properly formatted issues---> Converted and distributed by [TomeVault](https://tomevault.io/claim/kagenti) — claim your Tome and manage your conversions.

Frequently asked questions

Githubissues