set-up-my-support-info

Name: set-up-my-support-info
Availability: InStock
Author: akiotanaka847

Create and update support-context documents with routing rules and SLAs.

2|Updated May 8, 2026

Search Tags:#knowledge base #customer communication #support triage #routing rules #VIP handling #support onboarding #SLA response times

Ready to run

npx skills add https://github.com/akiotanaka847/qaio-desktop --skill set-up-my-support-info

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: set-up-my-support-info
Source: https://github.com/akiotanaka847/qaio-desktop/tree/main/store/agents/support/.agents/skills/set-up-my-support-info
Command: npx skills add https://github.com/akiotanaka847/qaio-desktop --skill set-up-my-support-info

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you define and maintain a shared support context—so support responses stay consistent with your product, customers, SLAs, routing rules, and known gotchas.

Core Features & Use Cases

Support context onboarding: Gathers the required basics (product overview, customer segments/VIP list, response-time targets, routing categories, and escalation tiers) through a short interview.
Context doc creation and updates: Creates or updates context/support-context.md so other skills can reliably read it before taking action.
Routing-ready playbook structure: Produces a routing rules section that maps inbound messages to the right targets (e.g., bug tracking, feature requests, outages, billing).

Quick Start

Tell me to set up our support context.

Frequently Asked Questions about set-up-my-support-info

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

FAQPage Schema

How do I create a shared support context document for consistent customer communication?▼

To create a shared support context, you complete a short interview to gather product overview, customer segments, SLA response times, routing rules, and known gotchas. The setup process writes these details atomically to a shared context document for consistent support triage.

What is the best way to define support routing rules and SLA response times for my product?▼

The best way to define SLA response times and routing rules is through a guided onboarding interview that maps inbound messages to correct targets like bug tracking, feature requests, and billing, then saves the playbook structure atomically to your support context file.

Can I update my existing support onboarding playbook when VIP handling or routing categories change?▼

Yes, you can update your support onboarding playbook when VIP handling or routing categories change. The skill optionally incorporates your existing support context file, confirms missing fields, and atomically writes updates to maintain consistent response quality.

How does support triage mapping work for inbound messages across different categories?▼

Support triage mapping works by producing a routing rules section that directs inbound messages to the right targets based on your defined categories, such as routing bug reports to bug tracking and feature requests to product teams, ensuring consistent response quality.

Do I need any existing configuration files to set up my support context and escalation tiers?▼

No existing files are required to set up support context and escalation tiers, but the skill can seed from an existing config/context-ledger.json and optionally incorporate an existing context/support-context.md file to pre-fill information during the interview.