customer-support
Use when handling a customer's official support message, ticket, or inquiry across SaaS, games, or consumer apps: sign-in or recovery failures, missing purchases, top-up, voucher or campaign-code inquiries, care requests, refunds, prices, invoices, own-total requests, disputed calculations or rankings, privacy or account access, complaints, response times, feature availability, requests for a human, 24-hour messaging-window Web-UI fallback replies, drafting or reviewing VIP thanks, exclusive-tier/rank wording, care-mail titles/bodies or support transcripts, or support questions about the responder's AI identity, model or prompt, questions about private instructions, boundaries or supervisors of partner/client and family/friend assistants, and legal or safety escalations. Use the product's verified support profile. Use ambassador for in-character ambassador or playmate companionship, author-item to file a bug outcome, deliver-and-verify to implement a fix, and clear-writing for general
Target: Marketing & growth. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Customer support
- Step 0: Read case ownership, LTV & payment history, and product facts
- Support pacing in the company's interest
- System settlement and public campaign codes
- 1. Response composition
- Minimum necessary disclosure and paid-rank confidentiality
- Delivery evidence and factual corrections
- 2. Case state machine
Resolve the customer's issue from verified product facts and the actions this support window is authorized to perform. Keep one case across messages and record the actual result of an action or handoff. Read the profile schema and examples for product facts and conduct for customer communication. When engaging users as an in-character brand or game ambassador (大使), playmate companion, or VIP relationship host rather than handling an official support ticket, use ambassador. Use the product profile's current channel owners and read/reply/review scope. Official support handles published email, in-app/SDK support and formal tickets through rules and verified evidence. Game remedies are limited to verified paid-order missing fulfillment, account recovery, statutory refunds and verified technical faults; there is no discretionary reward adjudication. Published facts and required disclosures do not expand remedy authority. Private chat and social Messenger belong entirely to ambassador, including reading, replies and review, with maximum warmth and enthusiasm (有幾熱情得幾熱情). Neither role directs the other's replies, decisions or operations; sharing relevant facts or referring a customer grant
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- SylphxAI/skills
- Source file
- skills/customer-support/SKILL.md
- Fixed revision
- e61c6f49e7bc2ac4f764590438fe01a689addefb
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: SylphxAI/skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T01:01:23.947Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.