Agent skill

Stale Ticket Triage

Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90…

MITAuto-check passedSales & Support

Install Stale Ticket Triage

skills CLI

$ npx skills add aozyildirim/Agena --skill stale-ticket-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install aozyildirim/Agena stale-ticket-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/aozyildirim/Agena.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agena/stale-ticket-triage .claude/skills/stale-ticket-triage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "stale-ticket-triage" agent skill from https://github.com/aozyildirim/Agena/tree/main/skills/agena/stale-ticket-triage into .claude/skills/stale-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stale-ticket-triage", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/aozyildirim/Agena/tree/main/skills/agena/stale-ticket-triage

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add aozyildirim/Agena --skill stale-ticket-triage -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install aozyildirim/Agena stale-ticket-triage --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aozyildirim/Agena.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/agena/stale-ticket-triage .agents/skills/stale-ticket-triage && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "stale-ticket-triage" agent skill from https://github.com/aozyildirim/Agena/tree/main/skills/agena/stale-ticket-triage into .agents/skills/stale-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stale-ticket-triage", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add aozyildirim/Agena --skill stale-ticket-triage -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install aozyildirim/Agena stale-ticket-triage --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aozyildirim/Agena.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/agena/stale-ticket-triage .cursor/skills/stale-ticket-triage && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "stale-ticket-triage" agent skill from https://github.com/aozyildirim/Agena/tree/main/skills/agena/stale-ticket-triage into .cursor/skills/stale-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stale-ticket-triage", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/aozyildirim/Agena.git --path skills/agena/stale-ticket-triage

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add aozyildirim/Agena --skill stale-ticket-triage -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install aozyildirim/Agena stale-ticket-triage --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aozyildirim/Agena.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/agena/stale-ticket-triage .gemini/skills/stale-ticket-triage && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "stale-ticket-triage" agent skill from https://github.com/aozyildirim/Agena/tree/main/skills/agena/stale-ticket-triage into .gemini/skills/stale-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stale-ticket-triage", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install aozyildirim/Agena stale-ticket-triage

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add aozyildirim/Agena --skill stale-ticket-triage -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/aozyildirim/Agena.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/agena/stale-ticket-triage .github/skills/stale-ticket-triage && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "stale-ticket-triage" agent skill from https://github.com/aozyildirim/Agena/tree/main/skills/agena/stale-ticket-triage into .github/skills/stale-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stale-ticket-triage", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add aozyildirim/Agena --skill stale-ticket-triage -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install aozyildirim/Agena stale-ticket-triage --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aozyildirim/Agena.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/agena/stale-ticket-triage .opencode/skills/stale-ticket-triage && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "stale-ticket-triage" agent skill from https://github.com/aozyildirim/Agena/tree/main/skills/agena/stale-ticket-triage into .opencode/skills/stale-ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stale-ticket-triage", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: stale-ticket-triage
GitHub stars: 103
Token cost: ~714 tokens
SKILL.md length: 335 words
Files: 1
Skills in repo: 5
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90…

Works in 5 steps: Define stale: a ticket is stale when its… → Schedule the scan (chip-pick: every 6h /… → System prompt the LLM with three… → …
Tasks that involve Customer support
SKILL.md covers How to apply this pattern, Example LLM reply format and Notes
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Stale Ticket Triage is an agent skill from aozyildirim/Agena. Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.

Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Customer support. The repository describes itself as: Agentic AI platform with pixel agent technology — autonomous code generation, PR automation & multi-tenant SaaS. The licence is MIT.

When your agent uses it

Tasks that involve Customer support

Example prompts

“look at every ticket older than X days”
“/stale-ticket-triage”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Define stale: a ticket is stale when its updated_at is older than
Schedule the scan (chip-pick: every 6h / 12h / daily 9am / weekly
System prompt the LLM with three explicit verdicts —
Persist each verdict as a triage decision row keyed by
One-click bulk approve in the UI: the human reviews the AI verdicts

What it can do on your machine

Read from SKILL.md and the folder at commit c4c92f8. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stale Ticket Triage loads about 714 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 335 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~60
When it runs · the whole SKILL.md, loaded when a task matches: ~714

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aozyildirim/Agena at commit c4c92f8, republished under its MIT licence (© aozyildirim). 335 words, ~714 tokens.

Download SKILL.mdSave it as .claude/skills/stale-ticket-triage/SKILL.md (or your agent's skills folder).

name: stale-ticket-triage
description: Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.
tags: project-management, jira, azure-devops, backlog-grooming, ai-agent
publisher: agena

Stale Ticket Triage

Backlogs accumulate dead rows. Most teams have a recurring Friday meeting where someone walks every ticket older than X days and decides whether to close, snooze, or keep it. That hour is the perfect AI workload — the decision is shallow but the volume is high.

How to apply this pattern

Define stale: a ticket is stale when its updated_at is older than the org's threshold (default 30 days) AND its status is still in the active set (not Closed / Done / Cancelled).
Schedule the scan (chip-pick: every 6h / 12h / daily 9am / weekly Sundays / monthly). Each run hits the source-platform API for every project the org cares about, lists stale issues, and sends each through a short LLM call.
System prompt the LLM with three explicit verdicts — close / snooze / keep — plus a one-sentence reason. Be conservative on close: only pick it when the ticket itself signals resolution (links a merged PR, mentions a follow-up). Default to snooze when unsure; never close from silence alone.
Persist each verdict as a triage decision row keyed by (org, source, external_id) so re-runs are idempotent. Status transitions: pending → applied / skipped / overridden.
One-click bulk approve in the UI: the human reviews the AI verdicts in a list, hits "Apply all AI suggestions", and the system writes back to Jira / Azure DevOps in a single batch.

Example LLM reply format

VERDICT: close
REASON: Closed by PR #4221 (merged 38 days ago); customer hasn't
        responded since the fix shipped.

VERDICT: snooze
REASON: Still relevant but no recent customer activity; revisit when
        the related epic resumes.

Notes

Audit trail is non-negotiable. Every AI verdict and every human override needs a row with timestamp + user id. Bulk-approve must not destroy history; it appends.
Source-side scan (read tickets directly from Jira / Azure DevOps) scales better than relying on imported task records, because most stale tickets were never imported into the AI tool.
Threshold is per-workspace. Solo product teams might want 14 days; enterprise backlogs need 60-90.
The verdict prompt is short on purpose — long prompts encourage the model to add commentary and skip the structured reply.
Pair with reporter-routing rules so security tickets bypass the triage flow entirely — those should never be auto-closed.

Files

Just SKILL.md in skills/agena/stale-ticket-triage of aozyildirim/Agena.

Open the folder on GitHubat commit c4c92f8

Compare with similar skills

Stale Ticket Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stale Ticket Triage compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Stale Ticket Triage this skillaozyildirim/Agena	103	—	~714	Automated safety check: Pass	MIT	2 days ago
Siftranknoperator/siftrank	225	—	~2.9k	Automated safety check: Pass	MIT	21 days ago
Supporthaacked/dotfiles	134	—	~2.9k	Automated safety check: Pass	None	yesterday
Customer Support Agentmastra-ai/mastra	29k	—	~2.2k	Automated safety check: Pass	Custom licence	today
Ticket TriageBevel-Software/Hexis	100	1 repos	~2.9k	Automated safety check: Pass	Apache-2.0	today
Add Agent Adaptersafedep/gryph	172	—	~679	Automated safety check: Pass	Apache-2.0	6 days ago

Similar skills

Siftrank
noperator/siftrank
Find needles in haystacks with SiftRank. An agent skill from noperator/siftrank.
225 GitHub stars~2.9k tokensUpdated 21 days ago
Sales & SupportAuto-check passed
Support
haacked/dotfiles
Support hero workflow — start a ticket investigation with auto-organized notes, find existing notes, or generate the weekly highlights log.
134 GitHub stars~2.9k tokensUpdated yesterday
Sales & SupportAuto-check passed
Customer Support Agent
mastra-ai/mastra
Authoring playbook for building agents that triage and reply to customer messages — support tickets, email inquiries, chat questions, refund requests, or product issues.
29k GitHub stars~2.2k tokensUpdated today
Sales & SupportAuto-check passed
Ticket Triage
Bevel-Software/Hexis
Triage and prioritize a support ticket or customer issue. An agent skill from Bevel-Software/Hexis.
100 GitHub starsUsed in 1 repo~2.9k tokens
Sales & SupportAuto-check passed
Add Agent Adapter
safedep/gryph
A skill your agent uses when adding support for a new AI coding agent to Gryph, or when changing how an existing agent adapter is wired.
172 GitHub stars~679 tokensUpdated 6 days ago
Sales & SupportAuto-check passed
Agent Support Matrix
jazzyalex/agent-sessions
Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility.
895 GitHub stars~587 tokensUpdated 2 days ago
Sales & SupportAuto-check passed

More from aozyildirim/Agena

Cross Source Correlation
aozyildirim/Agena
Correlate near-in-time events across PR merges, deploys, monitoring (Sentry/NewRelic/Datadog/AppDynamics) and ticket trackers (Jira/Azure DevOps) into confidence-scored clusters that answer "which…
103 GitHub stars~756 tokensUpdated 2 days ago
Auto-check passed
Integration Rule Engine
aozyildirim/Agena
A declarative routing engine that turns ticket / error attributes (reporter, label, project, area path, error class, environment) into a tag + AI agent + priority assignment, so cross-source…
103 GitHub stars~976 tokensUpdated 2 days ago
Auto-check passed
Owasp Reviewer Prompt
aozyildirim/Agena
A paranoid OWASP-Top-10-aware system prompt for AI code review that traces data flow, treats every input as malicious, maps each finding to an OWASP category, and outputs a structured Summary /…
103 GitHub stars~978 tokensUpdated 2 days ago
Auto-check passed
Review Backlog Killer
aozyildirim/Agena
Detect pull requests aging past warn / critical thresholds, score severity, and nudge reviewers via Slack DM, channel, email, or directly as a PR comment — with one-time auto-escalation when a PR…
103 GitHub stars~802 tokensUpdated 2 days ago
Auto-check passed

Questions about Stale Ticket Triage

What does Stale Ticket Triage do?

Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90…. Stale Ticket Triage is an agent skill from aozyildirim/Agena. Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.

When should I use Stale Ticket Triage?

Stale Ticket Triage fits situations like: tasks that involve Customer support.

How do I install Stale Ticket Triage in Claude Code?

Run `npx skills add aozyildirim/Agena --skill stale-ticket-triage -a claude-code`. Or copy the skill folder (skills/agena/stale-ticket-triage in aozyildirim/Agena) into .claude/skills/stale-ticket-triage in your project. Claude Code loads it when a task matches its description.

How do I install Stale Ticket Triage in Codex?

Run `npx skills add aozyildirim/Agena --skill stale-ticket-triage -a codex`. Or copy the skill folder (skills/agena/stale-ticket-triage in aozyildirim/Agena) into .agents/skills/stale-ticket-triage in your project. Codex loads it when a task matches its description.

Can I use Stale Ticket Triage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aozyildirim/Agena --skill stale-ticket-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stale-ticket-triage, .gemini/skills/stale-ticket-triage, .github/skills/stale-ticket-triage and .opencode/skills/stale-ticket-triage in your project.

What does Stale Ticket Triage need to run?

SKILL.md names no scripts, command-line tools or credentials: Stale Ticket Triage is instructions for the agent only.

Does Stale Ticket Triage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Stale Ticket Triage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Stale Ticket Triage use?

Stale Ticket Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Stale Ticket Triage use?

About 714 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Stale Ticket Triage?

Skills that share tags, products or a category with Stale Ticket Triage: Siftrank (noperator/siftrank, 225 stars), Support (haacked/dotfiles, 134 stars), Customer Support Agent (mastra-ai/mastra, 29k stars) and Ticket Triage (Bevel-Software/Hexis, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stale Ticket Triage?

aozyildirim (a GitHub user) maintains it in aozyildirim/Agena, which has 103 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.

Source: aozyildirim/Agena on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Stale Ticket Triage

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Stale Ticket Triage

How to apply this pattern

Example LLM reply format

Notes

Files

Compare with similar skills

Similar skills

More from aozyildirim/Agena

Related

Questions about Stale Ticket Triage