triage-issues
Use when a GitHub issue backlog needs read-only classification, prioritization, duplicate spotting, or clarification gaps called out.
Skill by nexttylabs
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/nexttylabs-triage-issues
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/triage-issues
What's inside
- Skill name
triage-issues- Description
- Use when a GitHub issue backlog needs read-only classification, prioritization, duplicate spotting, or clarification gaps called out.
- License
- MIT
- Instructions
- 59 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Triage Issues Use this skill for read-only issue analysis. ## Preconditions - `gh auth status` succeeds - The repository in GitHub matches the repository you intend to analyze ## Phase 1: Fetch Open Issues 1. Apply any label or milestone filters from the user. 2. Fetch open issues with `gh issue list`. 3. Read bodies and comments for the issues in scope. ## Phase 2: Classify For each issue, label it as: - bug - feature - chore - ambiguous Also rate whether it is: - well-specified - adequate - under-specified ## Phase 3: Rank - Rank bugs by impact, urgency, and scope - Rank features by value, effort, and readiness - Flag likely duplicates - Flag stale issues ## Phase 4: Report Return: - summary counts - top bugs - top features - under-specified issues - duplicates - stale items - 3 to 5 recommendations ## Output Format Use these sections in order: 1. Summary 2. Top priority bugs 3. Top opportunity features 4. Under-specified issues 5. Likely duplicates 6. Stale issues 7. Recommendations
From nexttylabs/kubebar, MIT.
More from nexttylabs/kubebar
- 0.598score
fix-issue
nexttylabs
Use when a GitHub issue should be handled end-to-end, including issue analysis, code changes, tests, verification, and an optional commit.
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
github
nexttylabs
Use when working with GitHub repositories, issues, pull requests, branches, or commits and the task needs authenticated repository operations or GitHub…
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
plan-mode
nexttylabs
Use when a task needs a written execution plan with explicit steps, risks, verification, and user approval before implementation starts.
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
pr-shepherd
nexttylabs
Use when a pull request needs one coordinated workflow covering review state, fixes, checks, branch updates, and merge readiness.
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
respond-pr
nexttylabs
Use when a pull request already has review feedback that needs triage, code changes, verification, and clear replies back to reviewers.
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
review-checklist
nexttylabs
Use when deciding whether a change is ready to merge and a concise cross-language checklist is more useful than a full narrative review.
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
review-pr
nexttylabs
Use when a pull request needs a serious pre-merge review covering correctness, edge cases, security, tests, documentation, and architecture.
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
triage-prs
nexttylabs
Use when open pull requests need a read-only dashboard showing review state, scope, blockers, conflicts, and merge readiness.
SkillAFreshness: A★ 2Claude Code +9 - 0.576score
ship
nexttylabs
Run the Swift iOS quality gate before shipping.
SkillAFreshness: A★ 2Claude Code +9
Signals
- Stars
- 2
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Apr 18, 2026 (6 months ago)
- Last release
- Oct 4, 2026 (25 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/nexttylabs/kubebar
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from nexttylabs
- 0.598score
fix-issue
nexttylabs
Use when a GitHub issue should be handled end-to-end, including issue analysis, code changes, tests, verification, and an optional commit.
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
github
nexttylabs
Use when working with GitHub repositories, issues, pull requests, branches, or commits and the task needs authenticated repository operations or GitHub…
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
plan-mode
nexttylabs
Use when a task needs a written execution plan with explicit steps, risks, verification, and user approval before implementation starts.
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
pr-shepherd
nexttylabs
Use when a pull request needs one coordinated workflow covering review state, fixes, checks, branch updates, and merge readiness.
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
respond-pr
nexttylabs
Use when a pull request already has review feedback that needs triage, code changes, verification, and clear replies back to reviewers.
SkillAFreshness: A★ 2Claude Code +9 - 0.598score
review-checklist
nexttylabs
Use when deciding whether a change is ready to merge and a concise cross-language checklist is more useful than a full narrative review.
SkillAFreshness: A★ 2Claude Code +9
Cite this page
triage-issues skill. Agent Mart. https://agentmart.dev/skills/nexttylabs-triage-issues (last updated 2026-10-24)