tune-my-routing

Rewrite support ticket routing rules and append an outputs.json record.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/akiotanaka847/qaio-desktop --skill tune-my-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tune-my-routing
Source: https://github.com/akiotanaka847/qaio-desktop/tree/main/store/agents/support/.agents/skills/tune-my-routing
Command: npx skills add https://github.com/akiotanaka847/qaio-desktop --skill tune-my-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fixes support inbox misrouting by letting you update the decision rules that classify tickets (bug vs feature request, categories, VIP handling) and route them to the right trackers, people, and playbooks.

Core Features & Use Cases

  • Rewrite routing rules from your current setup so updates preserve the decision-tree shape instead of starting from scratch.
  • Change classification logic by adjusting what qualifies as a bug vs a feature request and which categories exist.
  • Update routing destinations by changing tracker targets, refund approval ownership, and related escalation paths.
  • Keep downstream sections consistent by also updating VIP/segments and any gotchas that reference tracker or routing changes.

Quick Start

Tell the AI: "Update our routing so bug reports go to GitHub Issues, feature requests go to the requests queue, and refunds are approved by Alex."

Frequently Asked Questions about tune-my-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update support ticket routing rules for bug vs feature classification?

To update ticket routing rules, rewrite the existing decision-tree logic that classifies bugs versus feature requests and redirects them to the correct trackers. The process preserves your current setup while applying the new classification changes atomically.

What is the best way to reroute refund approval workflows in a support triage system?

The best way to reroute refund approvals is to update the support triage routing rules that define ownership and escalation paths. This changes exactly who receives the refund tickets while keeping downstream segments and related gotchas consistent.

How do support triage rules handle VIP ticket routing changes?

Support triage rules handle VIP routing by adjusting the specific segments within the decision tree. When you update the routing logic, the system ensures downstream sections remain consistent so VIP tickets reach the correct destinations without misrouting.

Can I adjust support triage categories without losing my existing integration targets?

Yes, you can adjust triage categories without losing existing integrations. The process validates connected integration targets before performing an atomic rewrite of the routing rules, ensuring your trackers and service connections remain intact during the update.

Why does support inbox misrouting happen when adding new ticket categories?

Support inbox misrouting happens when new ticket categories are added without updating the downstream gotchas and segments that reference the routing logic. Performing an atomic rewrite of the entire decision tree prevents these inconsistencies.