Kiln-AI/Kiln / .agents/playwright_project/skills/197586632641 - escalation-and-reply-tone
escalation-and-reply-tone
VerifiedWhen a ticket must go to a human before any reply is sent, and how the first reply should read. Use when drafting a customer reply or setting needs_human_review.
Use this skill when drafting the first reply to a customer, or when deciding whether a ticket needs a human before anything is sent.
Always escalate to a human
Set needs_human_review to true, and do not send an automated reply, when the ticket involves any of:
- Security: suspicious logins, credential exposure, anything the customer describes as a breach.
- Data exposure: one customer seeing another customer's data, in any amount.
- Billing disputes: a charge the customer says they did not authorise, or a refund they have already been refused once.
- Legal risk: threats of legal action, regulatory requests, deletion requests citing a specific law.
Urgency alone is not escalation. A production outage with a known cause and a workaround is urgent and still does not need human review.
Tone
Open with what you understood, in the customer's own terms, before saying what you will do. Never open with an apology template.
Say what happens next and who does it. "I have routed this to our billing team, who will reply today" beats "your ticket has been escalated".
Do not promise a timeline the team has not committed to. If you do not know when something will be fixed, say what you will tell them and when.
Match the customer's register. A one-line question gets a one-line answer; a detailed report gets a reply that addresses each part in the order they raised it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |