Agent skill · writing content · anthropics
draft-response
Draft a professional customer-facing response tailored to the situation and relationship. Use when answering a product question, responding to an escalation or outage, delivering bad news like a delay or won't-fix, declining a feature request, or replying to a billing issue.
Why this skill is useful
Adds a structured workflow for drafting tailored customer responses, incorporating context and relationship nuances that the AI wouldn't generate on its own.
What it needs
About 9k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.
What this skill does
/draft-response If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Draft a professional, customer-facing response tailored to the situation, customer relationship, and communication context. Usage Examples: /draft-response Acme Corp is asking when the new dashboard feature will ship /draft-response Customer escalation — their integration has been down for 2 days /draft-response Responding to a feature request we won't be building /draft-response Customer hit a billing error and wants a resolution ASAP Workflow 1. Understand the Context Parse the user's input to determine: Customer: Who is the communication for? Look up account context if available. Situation type: Question, issue, escalation, announcement, negotiation, bad news, good news, follow-up Urgency: Is this time-sensitive? How long has the customer been waiting? Channel: Email, support ticket, chat, or other (adjust formality accordingly) Relationship stage: New customer, established, frustrated/escalated Stakeholder level: End user, manager, executive, technical, business 2. Research Context Gather relevant background from available sources: ~~email: Previous correspondence with this customer on this topic Any commitments or timelines previously shared Tone and style of the existing thread ~~chat: Internal discussions about this customer or topic Any guidance from product, engineering, or leadership Similar situations and how they were handled ~~CRM (if connected): Account details and plan level Contact information and key stakeholders Previous escalations or sensitive issues ~~support platform (if connected): Related tickets and their resolution Known issues or workarounds SLA status and response time commitments ~~knowledge base: Official documentation or help articles to reference Product roadmap information (if shareable) Policy or process documentation 3. Generate the Draft Produce a response tailored to the situation: 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/draft-response