triage-issue
Reads and categorizes new repository issues, assigning appropriate labels and identifying technical severity.
Install
mkdir -p .claude/skills/triage-issue-dr5hn && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10886" && unzip -o skill.zip -d .claude/skills/triage-issue-dr5hn && rm skill.zipInstalls to .claude/skills/triage-issue-dr5hn
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Triage and classify new issues for the CSC database repository. Use this skill whenever an issue is opened, assigned to you, or needs classification. Trigger on: new issue triage, "classify this issue", "what type of issue is this", labelling requests, issue assignment, data correction reports, data addition requests, bug reports, feature requests, or any time you need to categorise, label, prioritise, or respond to a GitHub issue. Also use when deciding whether an issue can be auto-fixed or needs human intervention.Key capabilities
- →Classify issues
- →Apply labels
- →Assess severity
- →Determine action
How it works
Analyzes issue content to categorize, label, and prioritize them for the database repository.
Inputs & outputs
When to use triage-issue
- →Classifying new incoming issues
- →Labeling GitHub issues
- →Prioritizing support tickets
About this skill
Triage Process
Step 1: Classify the Issue
Read the issue title and description to determine the category:
| Category | Labels | Indicators |
|---|---|---|
| Data Correction | data-correction | "wrong", "incorrect", "outdated", "fix coordinates" |
| Data Addition | data-addition | "add", "missing", "new city/state", "not in database" |
| Bug Report | bug | "error", "crash", "not working", "broken" |
| Feature Request | enhancement | "would be nice", "please add", "feature", "suggestion" |
| Question | question | "how to", "is it possible", "what is", "?" |
| Documentation | documentation | "docs", "readme", "instructions", "guide" |
Step 2: Add Entity Labels
If the issue involves specific data entities, add:
data:cities- for city-related issuesdata:states- for state-related issuesdata:countries- for country-related issues
Step 3: Assess Severity
| Severity | Label | Criteria |
|---|---|---|
| Critical | critical | Country/state deletion, widespread data corruption |
| High | priority:high | Many cities affected, coordinate errors for major cities |
| Normal | (no label) | Individual city corrections, small additions |
| Low | priority:low | Cosmetic changes, optional field additions |
Step 4: Determine Action
Auto-fixable issues (label auto-fix, assign to @copilot):
- Simple coordinate corrections with source provided
- Missing optional fields that can be looked up
- Formatting issues in existing data
- Single record corrections with clear correct values
Needs contributor (label help-wanted):
- Large data additions requiring local knowledge
- Corrections without source documentation
- Issues in regions/countries where verification is difficult
Needs maintainer (assign to @dr5hn):
- Schema changes
- API-related issues
- Infrastructure/tooling issues
- State or country level changes
- Policy decisions
Step 5: Respond to the Issue
For data corrections:
Thanks for reporting this! I've classified this as a data correction for [entity type].
[If auto-fixable]: I'll work on a fix for this. A PR will be opened shortly.
[If needs contributor]: Would you like to submit a PR with this fix? Here's how:
1. Edit the relevant file in `contributions/` directory
2. Submit a PR with a link to an official source
You can also use our [CSC Update Tool](https://manager.countrystatecity.in/) for a guided process.
For data additions:
Thanks for requesting this addition!
To help us process this, please provide:
- The data in JSON format with required fields
- A link to an official source
- The number of records
Refer to our [Contribution Guidelines](https://github.com/dr5hn/countries-states-cities-database/blob/master/.github/CONTRIBUTING.md) for the required fields.
For bug reports:
Thanks for reporting this bug. I've tagged it for review.
[If additional info needed]: Could you please provide:
- Steps to reproduce
- Expected vs actual behaviour
- Which platform/tool you're using (API, JSON files, npm package)
Important Rules
- Always be polite and welcoming
- Do not close issues without maintainer approval
- Do not make promises about timelines
- For API issues, direct users to [email protected]
- For urgent data issues, apply the
priority:highlabel
When not to use it
- →Internal project management
Prerequisites
Limitations
- →Do not close issues without maintainer approval
How it compares
Automates the triage process for incoming issues.
Compared to similar skills
triage-issue side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| triage-issue (this skill) | 0 | 4mo | No flags | Beginner |
| linear | 10 | 2mo | No flags | Beginner |
| zapier-workflows | 11 | 8mo | Review | Beginner |
| attio-skill-generator | 7 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
linear
lobehub
Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
attio-skill-generator
kesslerio
Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.
automation-brainstorm
MacroMan5
Interactive workflow design advisor for Power Automate, n8n, Make, Zapier and other platforms. Guides users through planning automation workflows with smart questions about triggers, actions, data flow, and error handling. Uses research sub-agent to find best practices and generates detailed implementation plan. Triggers when user mentions "create workflow", "build flow", "design automation", "need ideas for", or describes workflow requirements without having a complete design.
daily-briefing
anthropics
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
jira
davila7
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.