RT (Request Tracker) agent skills for Claude Code, Cursor and RevampKey

4 ready-made playbooks that teach an AI agent how to do real RT (Request Tracker) work: which tools to call, what to check first, and when to stop and ask you.

Download RevampKey, free I have it: connect RT (Request Tracker)

Connect RT (Request Tracker) once and all 4 skills install themselves and stay up to date. Mac, Windows and Linux.

All 4 RT (Request Tracker) skills

Each skill is one job. You ask in plain words and the agent loads the skill that matches, then follows its steps.

Start hereAsks before writing17 RT (Request Tracker) tools

Use the RT connector safely

Sets up the RT Request Tracker connector: confirms which account will act, searches tickets with scoped queries, and asks for explicit approval before any write.

Use it when

Connecting RT for the first time and checking whose account is acting
Searching tickets in a queue without pulling the whole instance
Deciding whether a change should be an internal comment or a reply to the requestor

Tools it uses

get_current_user
get_queue
get_ticket
search_tickets
list_queues
get_ticket_history
get_transaction
get_ticket_attachments
get_attachment
save_attachment
get_queue_fields
lookup_user
get_ticketsql_grammar
create_ticket
update_ticket
add_comment
add_reply

Example

Connect to our RT and show me how many open tickets are in the Support queue.

Connected as jdoe (the account behind your auth token). The Support queue has 37 open tickets: 22 new and 15 open. I have not changed anything. Tell me if you want any of them updated.

Use in RevampKeyRead the full skill →

Read-only3 RT (Request Tracker) tools

Audit an RT queue's setup with AI

Reviews a Request Tracker queue's lifecycle, custom fields, groups, watchers and rights against the team's intended workflow, and lists gaps and duplicates. It proposes a fix plan and asks for explicit approval before changing anything.

Use it when

A new queue is about to go live and needs a configuration check
Requests are getting stuck or going to the wrong people
Someone asks who can see or act on a queue's tickets

Tools it uses

get_queue
get_queue_fields
lookup_user

Example

Audit the Billing Disputes queue setup against our workflow and tell me what's missing or duplicated.

Billing Disputes (queue 14) uses the shared Standard lifecycle, which is also used by 3 other queues, so I won't change it. Two findings block go-live: the Finance Review group is empty, and the Waiting on Customer status is missing. I also found a duplicate Customer field alongside Client. I've drafted a 5-step plan and will apply it only once you approve.

Use in RevampKeyRead the full skill →

Asks before writing10 RT (Request Tracker) tools

Investigate an RT ticket's history with AI

Reconstructs the transaction history of one RT ticket in time order, measures where the delay or repeated handoff occurred, and states a root cause with evidence. It asks before changing anything on the ticket.

Use it when

A ticket has sat open for weeks and you need to know where it stalled
You want a timeline of who changed the owner, status or due date
You need to check whether a reply actually reached the requestor or was left as an internal comment

Tools it uses

get_current_user
get_ticket
search_tickets
get_ticket_history
get_transaction
update_ticket
add_comment
add_reply
create_ticket
save_attachment

Example

Why did RT ticket 48213 take 41 days to resolve? Show me the timeline and where it stalled.

Ticket #48213 sat for 41 days, and the largest gap was 19 days between the requestor's last message and the first staff reply. It changed owner three times, and the second handoff happened with no work logged. The root cause is a ping-pong handoff that left the ticket unowned for most of that stretch. Confidence is medium because one call was logged outside RT. I have not changed the ticket; I can draft a chaser to the requestor if you want one.

Use in RevampKeyRead the full skill →

Read-only9 RT (Request Tracker) tools

Triage an RT queue's open tickets

Ranks a Request Tracker queue's open tickets by what needs action now: overdue, customer waiting, unowned, stale. Read-only; it drafts next steps and changes nothing.

Use it when

Before a team standup, to see what in a queue needs attention
When a queue feels backed up and you need the stale and unowned tickets
When you want to know which requestors are still waiting on a reply

Tools it uses

list_queues
get_queue
get_queue_fields
get_current_user
search_tickets
get_ticketsql_grammar
get_ticket
get_ticket_history
lookup_user

Example

Triage the Support queue. What needs action today?

Support has 84 active tickets. 6 are overdue, 9 are waiting on a reply from us, and 12 have no owner and were opened more than three working days ago. Ticket #48213 is overdue and unowned; the requestor wrote again yesterday with no response, so I'd assign it and reply today. I haven't changed anything.

Use in RevampKeyRead the full skill →

Get all 4 without copying a file

RevampKey adds the skills when you connect RT (Request Tracker), updates them for you and removes them when you disconnect.

Download RevampKey

How RT (Request Tracker) skills work

Connect RT (Request Tracker)
The RT (Request Tracker) MCP server gives the agent its tools.
Ask in plain words
“Audit the Billing Disputes queue setup against our workflow and tell me what's missing or duplicated.” Each SKILL.md says when it applies, so only the one that fits is loaded.
Approve any change
The agent calls the tools in order, checks its work, and shows you any change before it makes it.

How to install RT (Request Tracker) skills

In RevampKey the skills install themselves when you connect RT (Request Tracker). In other tools each skill is one folder with a SKILL.md file, and you also need the RT (Request Tracker) MCP server connected there.

About 1 minute · nothing to copy

Download RevampKey for Mac, Windows or Linux and sign in.
Open Connectors and connect RT (Request Tracker). All 4 skills come with it and stay up to date; they go away when you remove the connector.
Ask in plain language, for example “Audit the Billing Disputes queue setup against our workflow and tell me what's missing or duplicated.”
Download RevampKeyConnect RT (Request Tracker) · 1 click
Get RevampKey to connect RT (Request Tracker)
RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and RT (Request Tracker) is one click away with its skills already attached.
Download RevampKey
Not now? Use the skills in your current tool
for s in essentials queue-setup-audit ticket-history-investigation ticket-triage-queue-review; do curl -fsSL --create-dirs -o .claude/skills/rt-request-tracker-$s/SKILL.md https://revampkey.com/marketplace/rt-request-tracker/skills/$s/SKILL.md done
Other tools

Into this project’s .claude/skills folder

Connect the RT (Request Tracker) MCP server in Claude Code.

Run this in your project folder to add all 4 skills:

for s in essentials queue-setup-audit ticket-history-investigation ticket-triage-queue-review; do
  curl -fsSL --create-dirs -o .claude/skills/rt-request-tracker-$s/SKILL.md https://revampkey.com/marketplace/rt-request-tracker/skills/$s/SKILL.md
done

Ask in plain language, for example “Audit the Billing Disputes queue setup against our workflow and tell me what's missing or duplicated.”

Into the shared .agents/skills folder

Connect the RT (Request Tracker) MCP server in Cursor.

Run this in your project folder to add all 4 skills:

for s in essentials queue-setup-audit ticket-history-investigation ticket-triage-queue-review; do
  curl -fsSL --create-dirs -o .agents/skills/rt-request-tracker-$s/SKILL.md https://revampkey.com/marketplace/rt-request-tracker/skills/$s/SKILL.md
done

Ask in plain language, for example “Audit the Billing Disputes queue setup against our workflow and tell me what's missing or duplicated.”

Into the shared .agents/skills folder

Connect the RT (Request Tracker) MCP server in Codex.

Run this in your project folder to add all 4 skills:

for s in essentials queue-setup-audit ticket-history-investigation ticket-triage-queue-review; do
  curl -fsSL --create-dirs -o .agents/skills/rt-request-tracker-$s/SKILL.md https://revampkey.com/marketplace/rt-request-tracker/skills/$s/SKILL.md
done

Ask in plain language, for example “Audit the Billing Disputes queue setup against our workflow and tell me what's missing or duplicated.”

Into the shared .agents/skills folder

Connect the RT (Request Tracker) MCP server in VS Code.

Run this in your project folder to add all 4 skills:

for s in essentials queue-setup-audit ticket-history-investigation ticket-triage-queue-review; do
  curl -fsSL --create-dirs -o .agents/skills/rt-request-tracker-$s/SKILL.md https://revampkey.com/marketplace/rt-request-tracker/skills/$s/SKILL.md
done

Ask in plain language, for example “Audit the Billing Disputes queue setup against our workflow and tell me what's missing or duplicated.”

RevampKey or copy the files?

In RevampKey

One click when you connect RT (Request Tracker)
Updated for you when a skill improves
Removed when you disconnect
The MCP server is set up for you
800+ other connectors, same way

Download free

Copy into your project

One command per project
Run it again to get updates
You connect the RT (Request Tracker) MCP server yourself
Works in Claude Code, Cursor, Codex and VS Code

See the command

RT (Request Tracker) skills FAQ

What is a RT (Request Tracker) agent skill?

A SKILL.md file: a short playbook an AI agent loads when your request matches it. Each RT (Request Tracker) skill describes one job, which RT (Request Tracker) tools to use in which order, what to check first and when to stop and ask you.

Do the RT (Request Tracker) skills change anything on their own?

2 of the 4 only read. The others tell the agent to show you the change and wait for a yes before it creates, edits or deletes anything in RT (Request Tracker).

Which tools can use these skills?

Any agent that reads the open Agent Skills format: Claude Code, Cursor, Codex, VS Code with Copilot and RevampKey. In RevampKey they are attached when you connect RT (Request Tracker); elsewhere you copy the folders into your project or skills directory.

Do I need the RT (Request Tracker) MCP server too?

Yes. The skills tell the agent how to do the work; the RT (Request Tracker) MCP server gives it the tools to do it. The RT (Request Tracker) MCP setup guide covers every client.

RT (Request Tracker) MCP server setup · This page as Markdown

Put RT (Request Tracker)’s best workflows in your agent

Download RevampKey, connect RT (Request Tracker) and ask your first question in about a minute.

Download RevampKey Connect RT (Request Tracker) · 1 click

All 4 RT (Request Tracker) skills

Use the RT connector safely

Use it when

Tools it uses

Audit an RT queue's setup with AI

Use it when

Tools it uses

Investigate an RT ticket's history with AI

Use it when

Tools it uses

Triage an RT queue's open tickets

Use it when

Tools it uses

Get all 4 without copying a file

How RT (Request Tracker) skills work

How to install RT (Request Tracker) skills

RevampKey or copy the files?

In RevampKey

Copy into your project

RT (Request Tracker) skills FAQ

Put RT (Request Tracker)’s best workflows in your agent

Skills for related tools