Skip to content
Agentmart
Submit a tool

issue-triage

Skill by VinkuraAI

IndexedMIT★ 3
Write a review

Chalk Labs

Need help deploying issue-triage?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

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/vinkuraai-issue-triage

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.

We use your email only for this newsletter. Privacy

About

The publisher has not written a description yet.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill name
issue-triage
Description
None
License
MIT
Instructions
77 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • missing YAML frontmatter
  • name: missing
  • description: missing

Files (1)

  • SKILL.md

SKILL.md (first lines)

# GitHub Issue Triage

## Description
This skill enables Pallas to triage GitHub issues systematically: applying labels, assessing priority, identifying duplicates, requesting missing reproduction steps, and routing issues to the right people or milestones.

## When to Use
- When processing a backlog of new or unlabeled issues
- When a user asks "what should we work on next?"
- When a new issue comes in and needs to be assessed before it sits idle
- When doing a periodic issue grooming session

## Instructions
You are performing issue triage. Your goal is to ensure every issue has enough information to act on, is correctly categorized, and is assigned an appropriate priority.

**Step 1 — Read and Classify**
For each issue, determine the type:
- `BUG`: Something that worked and now doesn't, or behaves incorrectly
- `FEATURE`: A request for new functionality
- `IMPROVEMENT`: An enhancement to existing functionality
- `QUESTION`: A support request or clarification needed
- `DOCS`: Documentation is missing or incorrect
- `CHORE`: Dependency updates, CI fixes, cleanup

Apply the corresponding label.

**Step 2 — Check for Duplicates**
Search existing issues for similar reports. Look for:
- Same error message
- Same feature being requested
- Same component mentioned

If a duplicate is found: comment "Duplicate of #[issue number]", apply the `duplicate` label, and close the issue.

**Step 3 — Assess Completeness**
For `BUG` reports, verify these are present:
- Steps to reproduce
- Expected behavior
- Actual behavior
- Environment (OS, version, relevant config)
- Error messages or logs

If any are missing, apply `needs-more-info` label and post a comment requesting the specific missing information. Use this template:
```
Thanks for the report! To help us investigate, could you provide:
- [ ] Steps to reproduce
- [ ] Your environment (OS, version)
- [ ] The full error message/stack trace
```

**Step 4 — Priority Assessment**
Assign priority based on impact and urgency:
- `P0 — Critical`: Data loss, security vulnerability, complete feature broken in production
- `P1 — High`: Important feature broken, significant user impact, no workaround
- `P2 — Medium`: Feature degraded, workaround exists, affects some users
- `P3 — Low`: Minor inconvenience, cosmetic, rarely triggered edge case

**Step 5 — Routing**
- If the issue touches a specific module or component, apply the appropriate component label
- If it relates to an existing milestone, add it to that milestone
- If it is a good first issue for new contributors, add `good-first-issue` and ensure the description is complete

**Step 6 — Triage Summary**
After processing a batch of issues, produce a summary:
```
Triaged: N issues
  Bugs (P0): N
  Bugs (P1-P3): N
  Features: N
  Duplicates closed: N
  Needs more info: N
```

## Examples
- "Triage the 10 most recent issues in this repo."
- "Is issue #234 a duplicate? Find related issues."
- "Label and prioritize all unlabeled issues."

From VinkuraAI/Pallas-agent, MIT.

Signals

Stars
3
Forks
1
Open issues
0
Last commit (this folder)
Mar 17, 2026 (8 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get issue-triage running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying issue-triage?

CallGet help
Cite this page

issue-triage skill. Agent Mart. https://agentmart.dev/skills/vinkuraai-issue-triage (last updated 2026-10-24)