[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-draft-response":3,"mdc--8yeiq-key":34,"related-org-anthropic-draft-response":1541,"related-repo-anthropic-draft-response":1726},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":32,"mdContent":33},"draft-response","draft customer-facing responses","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"anthropic","Anthropic","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fanthropic.png","anthropics",[13,17,20],{"name":14,"slug":15,"type":16},"Writing","writing","tag",{"name":18,"slug":19,"type":16},"Customer Support","customer-support",{"name":21,"slug":22,"type":16},"Communications","communications",22885,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","2026-04-06T17:58:56.261538",null,2736,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":31},[],"Open source repository of plugins primarily intended for knowledge workers to use in Claude Cowork","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Ftree\u002FHEAD\u002Fcustomer-support\u002Fskills\u002Fdraft-response","---\nname: draft-response\ndescription: 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.\nargument-hint: \"\u003Csituation description>\"\n---\n\n# \u002Fdraft-response\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nDraft a professional, customer-facing response tailored to the situation, customer relationship, and communication context.\n\n## Usage\n\n```\n\u002Fdraft-response \u003Ccontext about the customer question, issue, or request>\n```\n\nExamples:\n- `\u002Fdraft-response Acme Corp is asking when the new dashboard feature will ship`\n- `\u002Fdraft-response Customer escalation — their integration has been down for 2 days`\n- `\u002Fdraft-response Responding to a feature request we won't be building`\n- `\u002Fdraft-response Customer hit a billing error and wants a resolution ASAP`\n\n## Workflow\n\n### 1. Understand the Context\n\nParse the user's input to determine:\n\n- **Customer**: Who is the communication for? Look up account context if available.\n- **Situation type**: Question, issue, escalation, announcement, negotiation, bad news, good news, follow-up\n- **Urgency**: Is this time-sensitive? How long has the customer been waiting?\n- **Channel**: Email, support ticket, chat, or other (adjust formality accordingly)\n- **Relationship stage**: New customer, established, frustrated\u002Fescalated\n- **Stakeholder level**: End user, manager, executive, technical, business\n\n### 2. Research Context\n\nGather relevant background from available sources:\n\n**~~email:**\n- Previous correspondence with this customer on this topic\n- Any commitments or timelines previously shared\n- Tone and style of the existing thread\n\n**~~chat:**\n- Internal discussions about this customer or topic\n- Any guidance from product, engineering, or leadership\n- Similar situations and how they were handled\n\n**~~CRM (if connected):**\n- Account details and plan level\n- Contact information and key stakeholders\n- Previous escalations or sensitive issues\n\n**~~support platform (if connected):**\n- Related tickets and their resolution\n- Known issues or workarounds\n- SLA status and response time commitments\n\n**~~knowledge base:**\n- Official documentation or help articles to reference\n- Product roadmap information (if shareable)\n- Policy or process documentation\n\n### 3. Generate the Draft\n\nProduce a response tailored to the situation:\n\n```\n## Draft Response\n\n**To:** [Customer contact name]\n**Re:** [Subject\u002Ftopic]\n**Channel:** [Email \u002F Ticket \u002F Chat]\n**Tone:** [Empathetic \u002F Professional \u002F Technical \u002F Celebratory \u002F Candid]\n\n---\n\n[Draft response text]\n\n---\n\n### Notes for You (internal — do not send)\n- **Why this approach:** [Rationale for tone and content choices]\n- **Things to verify:** [Any facts or commitments to confirm before sending]\n- **Risk factors:** [Anything sensitive about this response]\n- **Follow-up needed:** [Actions to take after sending]\n- **Escalation note:** [If this should be reviewed by someone else first]\n```\n\n### 4. Run Quality Checks\n\nBefore presenting the draft, verify:\n\n- [ ] Tone matches the situation and relationship\n- [ ] No commitments beyond what's authorized\n- [ ] No product roadmap details that shouldn't be shared externally\n- [ ] Accurate references to previous conversations\n- [ ] Clear next steps and ownership\n- [ ] Appropriate for the stakeholder level (not too technical for executives, not too vague for engineers)\n- [ ] Length is appropriate for the channel (shorter for chat, fuller for email)\n\n### 5. Offer Iterations\n\nAfter presenting the draft:\n- \"Want me to adjust the tone? (more formal, more casual, more empathetic, more direct)\"\n- \"Should I add or remove any specific points?\"\n- \"Want me to make this shorter\u002Flonger?\"\n- \"Should I draft a version for a different stakeholder?\"\n- \"Want me to draft the internal escalation note as well?\"\n- \"Should I prepare a follow-up message to send after [X days] if no response?\"\n\n---\n\n## Customer Communication Best Practices\n\n### Core Principles\n\n1. **Lead with empathy**: Acknowledge the customer's situation before jumping to solutions\n2. **Be direct**: Get to the point — customers are busy. Bottom-line-up-front.\n3. **Be honest**: Never overpromise, never mislead, never hide bad news in jargon\n4. **Be specific**: Use concrete details, timelines, and names — avoid vague language\n5. **Own it**: Take responsibility when appropriate. \"We\" not \"the system\" or \"the process\"\n6. **Close the loop**: Every response should have a clear next step or call to action\n7. **Match their energy**: If they're frustrated, be empathetic first. If they're excited, be enthusiastic.\n\n### Response Structure\n\nFor most customer communications, follow this structure:\n\n```\n1. Acknowledgment \u002F Context (1-2 sentences)\n   - Acknowledge what they said, asked, or are experiencing\n   - Show you understand their situation\n\n2. Core Message (1-3 paragraphs)\n   - Deliver the main information, answer, or update\n   - Be specific and concrete\n   - Include relevant details they need\n\n3. Next Steps (1-3 bullets)\n   - What YOU will do and by when\n   - What THEY need to do (if anything)\n   - When they'll hear from you next\n\n4. Closing (1 sentence)\n   - Warm but professional sign-off\n   - Reinforce you're available if needed\n```\n\n### Length Guidelines\n\n- **Chat\u002FIM**: 1-4 sentences. Get to the point immediately.\n- **Support ticket response**: 1-3 short paragraphs. Structured and scannable.\n- **Email**: 3-5 paragraphs max. Respect their inbox.\n- **Escalation response**: As long as needed to be thorough, but well-structured with headers.\n- **Executive communication**: Shorter is better. 2-3 paragraphs max. Data-driven.\n\n## Tone and Style Guidelines\n\n### Tone Spectrum\n\n| Situation | Tone | Characteristics |\n|-----------|------|----------------|\n| Good news \u002F wins | Celebratory | Enthusiastic, warm, congratulatory, forward-looking |\n| Routine update | Professional | Clear, concise, informative, friendly |\n| Technical response | Precise | Accurate, detailed, structured, patient |\n| Delayed delivery | Accountable | Honest, apologetic, action-oriented, specific |\n| Bad news | Candid | Direct, empathetic, solution-oriented, respectful |\n| Issue \u002F outage | Urgent | Immediate, transparent, actionable, reassuring |\n| Escalation | Executive | Composed, ownership-taking, plan-presenting, confident |\n| Billing \u002F account | Precise | Clear, factual, empathetic, resolution-focused |\n\n### Tone Adjustments by Relationship Stage\n\n**New Customer (0-3 months):**\n- More formal and professional\n- Extra context and explanation (don't assume knowledge)\n- Proactively offer help and resources\n- Build trust through reliability and responsiveness\n\n**Established Customer (3+ months):**\n- Warm and collaborative\n- Can reference shared history and previous conversations\n- More direct and efficient communication\n- Show awareness of their goals and priorities\n\n**Frustrated or Escalated Customer:**\n- Extra empathy and acknowledgment\n- Urgency in response times\n- Concrete action plans with specific commitments\n- Shorter feedback loops\n\n### Writing Style Rules\n\n**DO:**\n- Use active voice (\"We'll investigate\" not \"This will be investigated\")\n- Use \"I\" for personal commitments and \"we\" for team commitments\n- Name specific people when assigning actions (\"Sarah from our engineering team will...\")\n- Use the customer's terminology, not your internal jargon\n- Include specific dates and times, not relative terms (\"by Friday January 24\" not \"in a few days\")\n- Break up long responses with headers or bullet points\n\n**DON'T:**\n- Use corporate jargon or buzzwords (\"synergy\", \"leverage\", \"paradigm shift\")\n- Deflect blame to other teams, systems, or processes\n- Use passive voice to avoid ownership (\"Mistakes were made\")\n- Include unnecessary caveats or hedging that undermines confidence\n- CC people unnecessarily — only include those who need to be in the conversation\n- Use exclamation marks excessively (one per email max, if any)\n\n## Situation-Specific Approaches\n\n**Answering a product question:**\n- Lead with the direct answer\n- Provide relevant documentation links\n- Offer to connect them with the right resource if needed\n- If you don't know the answer: say so honestly, commit to finding out, give a timeline\n\n**Responding to an issue or bug:**\n- Acknowledge the impact on their work\n- State what you know about the issue and its status\n- Provide workaround if available\n- Set expectations for resolution timeline\n- Commit to updates at regular intervals\n\n**Handling an escalation:**\n- Acknowledge the severity and their frustration\n- Take ownership (no deflecting or excuse-making)\n- Provide a clear action plan with timeline\n- Identify the person accountable for resolution\n- Offer a meeting or call if appropriate for the severity\n\n**Delivering bad news (feature sunset, delay, can't-fix):**\n- Be direct — don't bury the news\n- Explain the reasoning honestly\n- Acknowledge the impact on them specifically\n- Offer alternatives or mitigation\n- Provide a clear path forward\n\n**Sharing good news (feature launch, milestone, recognition):**\n- Lead with the positive outcome\n- Connect it to their specific goals or use case\n- Suggest next steps to capitalize on the good news\n- Express genuine enthusiasm\n\n**Declining a request (feature request, discount, exception):**\n- Acknowledge the request and its reasoning\n- Be honest about the decision\n- Explain the why without being dismissive\n- Offer alternatives when possible\n- Leave the door open for future conversation\n\n## Response Templates for Common Scenarios\n\n### Acknowledging a Bug Report\n\n```\nHi [Name],\n\nThank you for reporting this — I can see how [specific impact] would be\nfrustrating for your team.\n\nI've confirmed the issue and escalated it to our engineering team as a\n[priority level]. Here's what we know so far:\n- [What's happening]\n- [What's causing it, if known]\n- [Workaround, if available]\n\nI'll update you by [specific date\u002Ftime] with a resolution timeline.\nIn the meantime, [workaround details if applicable].\n\nLet me know if you have any questions or if this is impacting you in\nother ways I should know about.\n\nBest,\n[Your name]\n```\n\n### Acknowledging a Billing or Account Issue\n\n```\nHi [Name],\n\nThank you for reaching out about this — I understand billing issues\nneed prompt attention, and I want to make sure this gets resolved\nquickly.\n\nI've looked into your account and here's what I'm seeing:\n- [What happened — clear factual explanation]\n- [Impact on their account — charges, access, etc.]\n\nHere's what I'm doing to fix this:\n- [Action 1 — with timeline]\n- [Action 2 — if applicable]\n\n[If resolution is immediate: \"This has been corrected and you should\nsee the change reflected within [timeframe].\"]\n[If needs investigation: \"I'm escalating this to our billing team\nand will have an update for you by [specific date].\"]\n\nI'm sorry for the inconvenience. Let me know if you have any\nquestions about your account.\n\nBest,\n[Your name]\n```\n\n### Responding to a Feature Request You Won't Build\n\n```\nHi [Name],\n\nThank you for sharing this request — I can see why [capability] would\nbe valuable for [their use case].\n\nI discussed this with our product team, and this isn't something we're\nplanning to build in the near term. The primary reason is [honest,\nrespectful explanation — e.g., it serves a narrow use case, it conflicts\nwith our architecture direction, etc.].\n\nThat said, I want to make sure you can accomplish your goal. Here are\nsome alternatives:\n- [Alternative approach 1]\n- [Alternative approach 2]\n- [Integration or workaround if applicable]\n\nI've also documented your request in our feedback system, and if our\ndirection changes, I'll let you know.\n\nWould any of these alternatives work for your team? Happy to dig\ndeeper into any of them.\n\nBest,\n[Your name]\n```\n\n### Outage or Incident Communication\n\n```\nHi [Name],\n\nI wanted to reach out directly to let you know about an issue affecting\n[service\u002Ffeature] that I know your team relies on.\n\n**What happened:** [Clear, non-technical explanation]\n**Impact:** [How it affects them specifically]\n**Status:** [Current status — investigating \u002F identified \u002F fixing \u002F resolved]\n**ETA for resolution:** [Specific time if known, or \"we'll update every X hours\"]\n\n[If applicable: \"In the meantime, you can [workaround].\"]\n\nI'm personally tracking this and will update you as soon as we have a\nresolution. You can also check [status page URL] for real-time updates.\n\nI'm sorry for the disruption to your team's work. We take this seriously\nand [what you're doing to prevent recurrence if known].\n\n[Your name]\n```\n\n### Following Up After Silence\n\n```\nHi [Name],\n\nI wanted to check in — I sent over [what you sent] on [date] and\nwanted to make sure it didn't get lost in the shuffle.\n\n[Brief reminder of what you need from them or what you're offering]\n\nIf now isn't a good time, no worries — just let me know when would be\nbetter, and I'm happy to reconnect then.\n\nBest,\n[Your name]\n```\n\n## Follow-up and Escalation Guidance\n\n### Follow-up Cadence\n\n| Situation | Follow-up Timing |\n|-----------|-----------------|\n| Unanswered question | 2-3 business days |\n| Open support issue | Daily until resolved for critical, 2-3 days for standard |\n| Post-meeting action items | Within 24 hours (send notes), then check at deadline |\n| General check-in | As needed for ongoing issues |\n| After delivering bad news | 1 week to check on impact and sentiment |\n\n### When to Escalate\n\n**Escalate to your manager when:**\n- Customer threatens to cancel or significantly downsell\n- Customer requests exception to policy you can't authorize\n- An issue has been unresolved for longer than SLA allows\n- Customer requests direct contact with leadership\n- You've made an error that needs senior involvement to resolve\n\n**Escalate to product\u002Fengineering when:**\n- Bug is critical and blocking the customer's business\n- Feature gap is causing a competitive loss\n- Customer has unique technical requirements beyond standard support\n- Integration issues require engineering investigation\n\n**Escalation format:**\n```\nESCALATION: [Customer Name] — [One-line summary]\n\nUrgency: [Critical \u002F High \u002F Medium]\nCustomer impact: [What's broken for them]\nHistory: [Brief background — 2-3 sentences]\nWhat I've tried: [Actions taken so far]\nWhat I need: [Specific help or decision needed]\nDeadline: [When this needs to be resolved by]\n```\n",{"data":35,"body":37},{"name":4,"description":6,"argument-hint":36},"\u003Csituation description>",{"type":38,"children":39},"root",[40,48,67,72,79,92,97,138,144,151,156,220,226,231,239,257,265,283,291,309,317,335,343,361,367,372,381,387,392,464,470,475,516,520,526,532,606,612,617,626,632,685,691,697,873,879,887,910,918,941,949,972,978,986,1019,1027,1060,1066,1074,1097,1105,1133,1141,1169,1177,1205,1213,1236,1244,1272,1278,1284,1293,1299,1308,1314,1323,1329,1338,1344,1353,1359,1365,1451,1457,1465,1493,1501,1524,1532],{"type":41,"tag":42,"props":43,"children":44},"element","h1",{"id":4},[45],{"type":46,"value":47},"text","\u002Fdraft-response",{"type":41,"tag":49,"props":50,"children":51},"blockquote",{},[52],{"type":41,"tag":53,"props":54,"children":55},"p",{},[56,58,65],{"type":46,"value":57},"If you see unfamiliar placeholders or need to check which tools are connected, see ",{"type":41,"tag":59,"props":60,"children":62},"a",{"href":61},"..\u002F..\u002FCONNECTORS.md",[63],{"type":46,"value":64},"CONNECTORS.md",{"type":46,"value":66},".",{"type":41,"tag":53,"props":68,"children":69},{},[70],{"type":46,"value":71},"Draft a professional, customer-facing response tailored to the situation, customer relationship, and communication context.",{"type":41,"tag":73,"props":74,"children":76},"h2",{"id":75},"usage",[77],{"type":46,"value":78},"Usage",{"type":41,"tag":80,"props":81,"children":85},"pre",{"className":82,"code":84,"language":46},[83],"language-text","\u002Fdraft-response \u003Ccontext about the customer question, issue, or request>\n",[86],{"type":41,"tag":87,"props":88,"children":90},"code",{"__ignoreMap":89},"",[91],{"type":46,"value":84},{"type":41,"tag":53,"props":93,"children":94},{},[95],{"type":46,"value":96},"Examples:",{"type":41,"tag":98,"props":99,"children":100},"ul",{},[101,111,120,129],{"type":41,"tag":102,"props":103,"children":104},"li",{},[105],{"type":41,"tag":87,"props":106,"children":108},{"className":107},[],[109],{"type":46,"value":110},"\u002Fdraft-response Acme Corp is asking when the new dashboard feature will ship",{"type":41,"tag":102,"props":112,"children":113},{},[114],{"type":41,"tag":87,"props":115,"children":117},{"className":116},[],[118],{"type":46,"value":119},"\u002Fdraft-response Customer escalation — their integration has been down for 2 days",{"type":41,"tag":102,"props":121,"children":122},{},[123],{"type":41,"tag":87,"props":124,"children":126},{"className":125},[],[127],{"type":46,"value":128},"\u002Fdraft-response Responding to a feature request we won't be building",{"type":41,"tag":102,"props":130,"children":131},{},[132],{"type":41,"tag":87,"props":133,"children":135},{"className":134},[],[136],{"type":46,"value":137},"\u002Fdraft-response Customer hit a billing error and wants a resolution ASAP",{"type":41,"tag":73,"props":139,"children":141},{"id":140},"workflow",[142],{"type":46,"value":143},"Workflow",{"type":41,"tag":145,"props":146,"children":148},"h3",{"id":147},"_1-understand-the-context",[149],{"type":46,"value":150},"1. Understand the Context",{"type":41,"tag":53,"props":152,"children":153},{},[154],{"type":46,"value":155},"Parse the user's input to determine:",{"type":41,"tag":98,"props":157,"children":158},{},[159,170,180,190,200,210],{"type":41,"tag":102,"props":160,"children":161},{},[162,168],{"type":41,"tag":163,"props":164,"children":165},"strong",{},[166],{"type":46,"value":167},"Customer",{"type":46,"value":169},": Who is the communication for? Look up account context if available.",{"type":41,"tag":102,"props":171,"children":172},{},[173,178],{"type":41,"tag":163,"props":174,"children":175},{},[176],{"type":46,"value":177},"Situation type",{"type":46,"value":179},": Question, issue, escalation, announcement, negotiation, bad news, good news, follow-up",{"type":41,"tag":102,"props":181,"children":182},{},[183,188],{"type":41,"tag":163,"props":184,"children":185},{},[186],{"type":46,"value":187},"Urgency",{"type":46,"value":189},": Is this time-sensitive? How long has the customer been waiting?",{"type":41,"tag":102,"props":191,"children":192},{},[193,198],{"type":41,"tag":163,"props":194,"children":195},{},[196],{"type":46,"value":197},"Channel",{"type":46,"value":199},": Email, support ticket, chat, or other (adjust formality accordingly)",{"type":41,"tag":102,"props":201,"children":202},{},[203,208],{"type":41,"tag":163,"props":204,"children":205},{},[206],{"type":46,"value":207},"Relationship stage",{"type":46,"value":209},": New customer, established, frustrated\u002Fescalated",{"type":41,"tag":102,"props":211,"children":212},{},[213,218],{"type":41,"tag":163,"props":214,"children":215},{},[216],{"type":46,"value":217},"Stakeholder level",{"type":46,"value":219},": End user, manager, executive, technical, business",{"type":41,"tag":145,"props":221,"children":223},{"id":222},"_2-research-context",[224],{"type":46,"value":225},"2. Research Context",{"type":41,"tag":53,"props":227,"children":228},{},[229],{"type":46,"value":230},"Gather relevant background from available sources:",{"type":41,"tag":53,"props":232,"children":233},{},[234],{"type":41,"tag":163,"props":235,"children":236},{},[237],{"type":46,"value":238},"~~email:",{"type":41,"tag":98,"props":240,"children":241},{},[242,247,252],{"type":41,"tag":102,"props":243,"children":244},{},[245],{"type":46,"value":246},"Previous correspondence with this customer on this topic",{"type":41,"tag":102,"props":248,"children":249},{},[250],{"type":46,"value":251},"Any commitments or timelines previously shared",{"type":41,"tag":102,"props":253,"children":254},{},[255],{"type":46,"value":256},"Tone and style of the existing thread",{"type":41,"tag":53,"props":258,"children":259},{},[260],{"type":41,"tag":163,"props":261,"children":262},{},[263],{"type":46,"value":264},"~~chat:",{"type":41,"tag":98,"props":266,"children":267},{},[268,273,278],{"type":41,"tag":102,"props":269,"children":270},{},[271],{"type":46,"value":272},"Internal discussions about this customer or topic",{"type":41,"tag":102,"props":274,"children":275},{},[276],{"type":46,"value":277},"Any guidance from product, engineering, or leadership",{"type":41,"tag":102,"props":279,"children":280},{},[281],{"type":46,"value":282},"Similar situations and how they were handled",{"type":41,"tag":53,"props":284,"children":285},{},[286],{"type":41,"tag":163,"props":287,"children":288},{},[289],{"type":46,"value":290},"~~CRM (if connected):",{"type":41,"tag":98,"props":292,"children":293},{},[294,299,304],{"type":41,"tag":102,"props":295,"children":296},{},[297],{"type":46,"value":298},"Account details and plan level",{"type":41,"tag":102,"props":300,"children":301},{},[302],{"type":46,"value":303},"Contact information and key stakeholders",{"type":41,"tag":102,"props":305,"children":306},{},[307],{"type":46,"value":308},"Previous escalations or sensitive issues",{"type":41,"tag":53,"props":310,"children":311},{},[312],{"type":41,"tag":163,"props":313,"children":314},{},[315],{"type":46,"value":316},"~~support platform (if connected):",{"type":41,"tag":98,"props":318,"children":319},{},[320,325,330],{"type":41,"tag":102,"props":321,"children":322},{},[323],{"type":46,"value":324},"Related tickets and their resolution",{"type":41,"tag":102,"props":326,"children":327},{},[328],{"type":46,"value":329},"Known issues or workarounds",{"type":41,"tag":102,"props":331,"children":332},{},[333],{"type":46,"value":334},"SLA status and response time commitments",{"type":41,"tag":53,"props":336,"children":337},{},[338],{"type":41,"tag":163,"props":339,"children":340},{},[341],{"type":46,"value":342},"~~knowledge base:",{"type":41,"tag":98,"props":344,"children":345},{},[346,351,356],{"type":41,"tag":102,"props":347,"children":348},{},[349],{"type":46,"value":350},"Official documentation or help articles to reference",{"type":41,"tag":102,"props":352,"children":353},{},[354],{"type":46,"value":355},"Product roadmap information (if shareable)",{"type":41,"tag":102,"props":357,"children":358},{},[359],{"type":46,"value":360},"Policy or process documentation",{"type":41,"tag":145,"props":362,"children":364},{"id":363},"_3-generate-the-draft",[365],{"type":46,"value":366},"3. Generate the Draft",{"type":41,"tag":53,"props":368,"children":369},{},[370],{"type":46,"value":371},"Produce a response tailored to the situation:",{"type":41,"tag":80,"props":373,"children":376},{"className":374,"code":375,"language":46},[83],"## Draft Response\n\n**To:** [Customer contact name]\n**Re:** [Subject\u002Ftopic]\n**Channel:** [Email \u002F Ticket \u002F Chat]\n**Tone:** [Empathetic \u002F Professional \u002F Technical \u002F Celebratory \u002F Candid]\n\n---\n\n[Draft response text]\n\n---\n\n### Notes for You (internal — do not send)\n- **Why this approach:** [Rationale for tone and content choices]\n- **Things to verify:** [Any facts or commitments to confirm before sending]\n- **Risk factors:** [Anything sensitive about this response]\n- **Follow-up needed:** [Actions to take after sending]\n- **Escalation note:** [If this should be reviewed by someone else first]\n",[377],{"type":41,"tag":87,"props":378,"children":379},{"__ignoreMap":89},[380],{"type":46,"value":375},{"type":41,"tag":145,"props":382,"children":384},{"id":383},"_4-run-quality-checks",[385],{"type":46,"value":386},"4. Run Quality Checks",{"type":41,"tag":53,"props":388,"children":389},{},[390],{"type":46,"value":391},"Before presenting the draft, verify:",{"type":41,"tag":98,"props":393,"children":396},{"className":394},[395],"contains-task-list",[397,410,419,428,437,446,455],{"type":41,"tag":102,"props":398,"children":401},{"className":399},[400],"task-list-item",[402,408],{"type":41,"tag":403,"props":404,"children":407},"input",{"disabled":405,"type":406},true,"checkbox",[],{"type":46,"value":409}," Tone matches the situation and relationship",{"type":41,"tag":102,"props":411,"children":413},{"className":412},[400],[414,417],{"type":41,"tag":403,"props":415,"children":416},{"disabled":405,"type":406},[],{"type":46,"value":418}," No commitments beyond what's authorized",{"type":41,"tag":102,"props":420,"children":422},{"className":421},[400],[423,426],{"type":41,"tag":403,"props":424,"children":425},{"disabled":405,"type":406},[],{"type":46,"value":427}," No product roadmap details that shouldn't be shared externally",{"type":41,"tag":102,"props":429,"children":431},{"className":430},[400],[432,435],{"type":41,"tag":403,"props":433,"children":434},{"disabled":405,"type":406},[],{"type":46,"value":436}," Accurate references to previous conversations",{"type":41,"tag":102,"props":438,"children":440},{"className":439},[400],[441,444],{"type":41,"tag":403,"props":442,"children":443},{"disabled":405,"type":406},[],{"type":46,"value":445}," Clear next steps and ownership",{"type":41,"tag":102,"props":447,"children":449},{"className":448},[400],[450,453],{"type":41,"tag":403,"props":451,"children":452},{"disabled":405,"type":406},[],{"type":46,"value":454}," Appropriate for the stakeholder level (not too technical for executives, not too vague for engineers)",{"type":41,"tag":102,"props":456,"children":458},{"className":457},[400],[459,462],{"type":41,"tag":403,"props":460,"children":461},{"disabled":405,"type":406},[],{"type":46,"value":463}," Length is appropriate for the channel (shorter for chat, fuller for email)",{"type":41,"tag":145,"props":465,"children":467},{"id":466},"_5-offer-iterations",[468],{"type":46,"value":469},"5. Offer Iterations",{"type":41,"tag":53,"props":471,"children":472},{},[473],{"type":46,"value":474},"After presenting the draft:",{"type":41,"tag":98,"props":476,"children":477},{},[478,483,488,493,498,503],{"type":41,"tag":102,"props":479,"children":480},{},[481],{"type":46,"value":482},"\"Want me to adjust the tone? (more formal, more casual, more empathetic, more direct)\"",{"type":41,"tag":102,"props":484,"children":485},{},[486],{"type":46,"value":487},"\"Should I add or remove any specific points?\"",{"type":41,"tag":102,"props":489,"children":490},{},[491],{"type":46,"value":492},"\"Want me to make this shorter\u002Flonger?\"",{"type":41,"tag":102,"props":494,"children":495},{},[496],{"type":46,"value":497},"\"Should I draft a version for a different stakeholder?\"",{"type":41,"tag":102,"props":499,"children":500},{},[501],{"type":46,"value":502},"\"Want me to draft the internal escalation note as well?\"",{"type":41,"tag":102,"props":504,"children":505},{},[506,508,514],{"type":46,"value":507},"\"Should I prepare a follow-up message to send after ",{"type":41,"tag":509,"props":510,"children":511},"span",{},[512],{"type":46,"value":513},"X days",{"type":46,"value":515}," if no response?\"",{"type":41,"tag":517,"props":518,"children":519},"hr",{},[],{"type":41,"tag":73,"props":521,"children":523},{"id":522},"customer-communication-best-practices",[524],{"type":46,"value":525},"Customer Communication Best Practices",{"type":41,"tag":145,"props":527,"children":529},{"id":528},"core-principles",[530],{"type":46,"value":531},"Core Principles",{"type":41,"tag":533,"props":534,"children":535},"ol",{},[536,546,556,566,576,586,596],{"type":41,"tag":102,"props":537,"children":538},{},[539,544],{"type":41,"tag":163,"props":540,"children":541},{},[542],{"type":46,"value":543},"Lead with empathy",{"type":46,"value":545},": Acknowledge the customer's situation before jumping to solutions",{"type":41,"tag":102,"props":547,"children":548},{},[549,554],{"type":41,"tag":163,"props":550,"children":551},{},[552],{"type":46,"value":553},"Be direct",{"type":46,"value":555},": Get to the point — customers are busy. Bottom-line-up-front.",{"type":41,"tag":102,"props":557,"children":558},{},[559,564],{"type":41,"tag":163,"props":560,"children":561},{},[562],{"type":46,"value":563},"Be honest",{"type":46,"value":565},": Never overpromise, never mislead, never hide bad news in jargon",{"type":41,"tag":102,"props":567,"children":568},{},[569,574],{"type":41,"tag":163,"props":570,"children":571},{},[572],{"type":46,"value":573},"Be specific",{"type":46,"value":575},": Use concrete details, timelines, and names — avoid vague language",{"type":41,"tag":102,"props":577,"children":578},{},[579,584],{"type":41,"tag":163,"props":580,"children":581},{},[582],{"type":46,"value":583},"Own it",{"type":46,"value":585},": Take responsibility when appropriate. \"We\" not \"the system\" or \"the process\"",{"type":41,"tag":102,"props":587,"children":588},{},[589,594],{"type":41,"tag":163,"props":590,"children":591},{},[592],{"type":46,"value":593},"Close the loop",{"type":46,"value":595},": Every response should have a clear next step or call to action",{"type":41,"tag":102,"props":597,"children":598},{},[599,604],{"type":41,"tag":163,"props":600,"children":601},{},[602],{"type":46,"value":603},"Match their energy",{"type":46,"value":605},": If they're frustrated, be empathetic first. If they're excited, be enthusiastic.",{"type":41,"tag":145,"props":607,"children":609},{"id":608},"response-structure",[610],{"type":46,"value":611},"Response Structure",{"type":41,"tag":53,"props":613,"children":614},{},[615],{"type":46,"value":616},"For most customer communications, follow this structure:",{"type":41,"tag":80,"props":618,"children":621},{"className":619,"code":620,"language":46},[83],"1. Acknowledgment \u002F Context (1-2 sentences)\n   - Acknowledge what they said, asked, or are experiencing\n   - Show you understand their situation\n\n2. Core Message (1-3 paragraphs)\n   - Deliver the main information, answer, or update\n   - Be specific and concrete\n   - Include relevant details they need\n\n3. Next Steps (1-3 bullets)\n   - What YOU will do and by when\n   - What THEY need to do (if anything)\n   - When they'll hear from you next\n\n4. Closing (1 sentence)\n   - Warm but professional sign-off\n   - Reinforce you're available if needed\n",[622],{"type":41,"tag":87,"props":623,"children":624},{"__ignoreMap":89},[625],{"type":46,"value":620},{"type":41,"tag":145,"props":627,"children":629},{"id":628},"length-guidelines",[630],{"type":46,"value":631},"Length Guidelines",{"type":41,"tag":98,"props":633,"children":634},{},[635,645,655,665,675],{"type":41,"tag":102,"props":636,"children":637},{},[638,643],{"type":41,"tag":163,"props":639,"children":640},{},[641],{"type":46,"value":642},"Chat\u002FIM",{"type":46,"value":644},": 1-4 sentences. Get to the point immediately.",{"type":41,"tag":102,"props":646,"children":647},{},[648,653],{"type":41,"tag":163,"props":649,"children":650},{},[651],{"type":46,"value":652},"Support ticket response",{"type":46,"value":654},": 1-3 short paragraphs. Structured and scannable.",{"type":41,"tag":102,"props":656,"children":657},{},[658,663],{"type":41,"tag":163,"props":659,"children":660},{},[661],{"type":46,"value":662},"Email",{"type":46,"value":664},": 3-5 paragraphs max. Respect their inbox.",{"type":41,"tag":102,"props":666,"children":667},{},[668,673],{"type":41,"tag":163,"props":669,"children":670},{},[671],{"type":46,"value":672},"Escalation response",{"type":46,"value":674},": As long as needed to be thorough, but well-structured with headers.",{"type":41,"tag":102,"props":676,"children":677},{},[678,683],{"type":41,"tag":163,"props":679,"children":680},{},[681],{"type":46,"value":682},"Executive communication",{"type":46,"value":684},": Shorter is better. 2-3 paragraphs max. Data-driven.",{"type":41,"tag":73,"props":686,"children":688},{"id":687},"tone-and-style-guidelines",[689],{"type":46,"value":690},"Tone and Style Guidelines",{"type":41,"tag":145,"props":692,"children":694},{"id":693},"tone-spectrum",[695],{"type":46,"value":696},"Tone Spectrum",{"type":41,"tag":698,"props":699,"children":700},"table",{},[701,725],{"type":41,"tag":702,"props":703,"children":704},"thead",{},[705],{"type":41,"tag":706,"props":707,"children":708},"tr",{},[709,715,720],{"type":41,"tag":710,"props":711,"children":712},"th",{},[713],{"type":46,"value":714},"Situation",{"type":41,"tag":710,"props":716,"children":717},{},[718],{"type":46,"value":719},"Tone",{"type":41,"tag":710,"props":721,"children":722},{},[723],{"type":46,"value":724},"Characteristics",{"type":41,"tag":726,"props":727,"children":728},"tbody",{},[729,748,766,784,802,820,838,856],{"type":41,"tag":706,"props":730,"children":731},{},[732,738,743],{"type":41,"tag":733,"props":734,"children":735},"td",{},[736],{"type":46,"value":737},"Good news \u002F wins",{"type":41,"tag":733,"props":739,"children":740},{},[741],{"type":46,"value":742},"Celebratory",{"type":41,"tag":733,"props":744,"children":745},{},[746],{"type":46,"value":747},"Enthusiastic, warm, congratulatory, forward-looking",{"type":41,"tag":706,"props":749,"children":750},{},[751,756,761],{"type":41,"tag":733,"props":752,"children":753},{},[754],{"type":46,"value":755},"Routine update",{"type":41,"tag":733,"props":757,"children":758},{},[759],{"type":46,"value":760},"Professional",{"type":41,"tag":733,"props":762,"children":763},{},[764],{"type":46,"value":765},"Clear, concise, informative, friendly",{"type":41,"tag":706,"props":767,"children":768},{},[769,774,779],{"type":41,"tag":733,"props":770,"children":771},{},[772],{"type":46,"value":773},"Technical response",{"type":41,"tag":733,"props":775,"children":776},{},[777],{"type":46,"value":778},"Precise",{"type":41,"tag":733,"props":780,"children":781},{},[782],{"type":46,"value":783},"Accurate, detailed, structured, patient",{"type":41,"tag":706,"props":785,"children":786},{},[787,792,797],{"type":41,"tag":733,"props":788,"children":789},{},[790],{"type":46,"value":791},"Delayed delivery",{"type":41,"tag":733,"props":793,"children":794},{},[795],{"type":46,"value":796},"Accountable",{"type":41,"tag":733,"props":798,"children":799},{},[800],{"type":46,"value":801},"Honest, apologetic, action-oriented, specific",{"type":41,"tag":706,"props":803,"children":804},{},[805,810,815],{"type":41,"tag":733,"props":806,"children":807},{},[808],{"type":46,"value":809},"Bad news",{"type":41,"tag":733,"props":811,"children":812},{},[813],{"type":46,"value":814},"Candid",{"type":41,"tag":733,"props":816,"children":817},{},[818],{"type":46,"value":819},"Direct, empathetic, solution-oriented, respectful",{"type":41,"tag":706,"props":821,"children":822},{},[823,828,833],{"type":41,"tag":733,"props":824,"children":825},{},[826],{"type":46,"value":827},"Issue \u002F outage",{"type":41,"tag":733,"props":829,"children":830},{},[831],{"type":46,"value":832},"Urgent",{"type":41,"tag":733,"props":834,"children":835},{},[836],{"type":46,"value":837},"Immediate, transparent, actionable, reassuring",{"type":41,"tag":706,"props":839,"children":840},{},[841,846,851],{"type":41,"tag":733,"props":842,"children":843},{},[844],{"type":46,"value":845},"Escalation",{"type":41,"tag":733,"props":847,"children":848},{},[849],{"type":46,"value":850},"Executive",{"type":41,"tag":733,"props":852,"children":853},{},[854],{"type":46,"value":855},"Composed, ownership-taking, plan-presenting, confident",{"type":41,"tag":706,"props":857,"children":858},{},[859,864,868],{"type":41,"tag":733,"props":860,"children":861},{},[862],{"type":46,"value":863},"Billing \u002F account",{"type":41,"tag":733,"props":865,"children":866},{},[867],{"type":46,"value":778},{"type":41,"tag":733,"props":869,"children":870},{},[871],{"type":46,"value":872},"Clear, factual, empathetic, resolution-focused",{"type":41,"tag":145,"props":874,"children":876},{"id":875},"tone-adjustments-by-relationship-stage",[877],{"type":46,"value":878},"Tone Adjustments by Relationship Stage",{"type":41,"tag":53,"props":880,"children":881},{},[882],{"type":41,"tag":163,"props":883,"children":884},{},[885],{"type":46,"value":886},"New Customer (0-3 months):",{"type":41,"tag":98,"props":888,"children":889},{},[890,895,900,905],{"type":41,"tag":102,"props":891,"children":892},{},[893],{"type":46,"value":894},"More formal and professional",{"type":41,"tag":102,"props":896,"children":897},{},[898],{"type":46,"value":899},"Extra context and explanation (don't assume knowledge)",{"type":41,"tag":102,"props":901,"children":902},{},[903],{"type":46,"value":904},"Proactively offer help and resources",{"type":41,"tag":102,"props":906,"children":907},{},[908],{"type":46,"value":909},"Build trust through reliability and responsiveness",{"type":41,"tag":53,"props":911,"children":912},{},[913],{"type":41,"tag":163,"props":914,"children":915},{},[916],{"type":46,"value":917},"Established Customer (3+ months):",{"type":41,"tag":98,"props":919,"children":920},{},[921,926,931,936],{"type":41,"tag":102,"props":922,"children":923},{},[924],{"type":46,"value":925},"Warm and collaborative",{"type":41,"tag":102,"props":927,"children":928},{},[929],{"type":46,"value":930},"Can reference shared history and previous conversations",{"type":41,"tag":102,"props":932,"children":933},{},[934],{"type":46,"value":935},"More direct and efficient communication",{"type":41,"tag":102,"props":937,"children":938},{},[939],{"type":46,"value":940},"Show awareness of their goals and priorities",{"type":41,"tag":53,"props":942,"children":943},{},[944],{"type":41,"tag":163,"props":945,"children":946},{},[947],{"type":46,"value":948},"Frustrated or Escalated Customer:",{"type":41,"tag":98,"props":950,"children":951},{},[952,957,962,967],{"type":41,"tag":102,"props":953,"children":954},{},[955],{"type":46,"value":956},"Extra empathy and acknowledgment",{"type":41,"tag":102,"props":958,"children":959},{},[960],{"type":46,"value":961},"Urgency in response times",{"type":41,"tag":102,"props":963,"children":964},{},[965],{"type":46,"value":966},"Concrete action plans with specific commitments",{"type":41,"tag":102,"props":968,"children":969},{},[970],{"type":46,"value":971},"Shorter feedback loops",{"type":41,"tag":145,"props":973,"children":975},{"id":974},"writing-style-rules",[976],{"type":46,"value":977},"Writing Style Rules",{"type":41,"tag":53,"props":979,"children":980},{},[981],{"type":41,"tag":163,"props":982,"children":983},{},[984],{"type":46,"value":985},"DO:",{"type":41,"tag":98,"props":987,"children":988},{},[989,994,999,1004,1009,1014],{"type":41,"tag":102,"props":990,"children":991},{},[992],{"type":46,"value":993},"Use active voice (\"We'll investigate\" not \"This will be investigated\")",{"type":41,"tag":102,"props":995,"children":996},{},[997],{"type":46,"value":998},"Use \"I\" for personal commitments and \"we\" for team commitments",{"type":41,"tag":102,"props":1000,"children":1001},{},[1002],{"type":46,"value":1003},"Name specific people when assigning actions (\"Sarah from our engineering team will...\")",{"type":41,"tag":102,"props":1005,"children":1006},{},[1007],{"type":46,"value":1008},"Use the customer's terminology, not your internal jargon",{"type":41,"tag":102,"props":1010,"children":1011},{},[1012],{"type":46,"value":1013},"Include specific dates and times, not relative terms (\"by Friday January 24\" not \"in a few days\")",{"type":41,"tag":102,"props":1015,"children":1016},{},[1017],{"type":46,"value":1018},"Break up long responses with headers or bullet points",{"type":41,"tag":53,"props":1020,"children":1021},{},[1022],{"type":41,"tag":163,"props":1023,"children":1024},{},[1025],{"type":46,"value":1026},"DON'T:",{"type":41,"tag":98,"props":1028,"children":1029},{},[1030,1035,1040,1045,1050,1055],{"type":41,"tag":102,"props":1031,"children":1032},{},[1033],{"type":46,"value":1034},"Use corporate jargon or buzzwords (\"synergy\", \"leverage\", \"paradigm shift\")",{"type":41,"tag":102,"props":1036,"children":1037},{},[1038],{"type":46,"value":1039},"Deflect blame to other teams, systems, or processes",{"type":41,"tag":102,"props":1041,"children":1042},{},[1043],{"type":46,"value":1044},"Use passive voice to avoid ownership (\"Mistakes were made\")",{"type":41,"tag":102,"props":1046,"children":1047},{},[1048],{"type":46,"value":1049},"Include unnecessary caveats or hedging that undermines confidence",{"type":41,"tag":102,"props":1051,"children":1052},{},[1053],{"type":46,"value":1054},"CC people unnecessarily — only include those who need to be in the conversation",{"type":41,"tag":102,"props":1056,"children":1057},{},[1058],{"type":46,"value":1059},"Use exclamation marks excessively (one per email max, if any)",{"type":41,"tag":73,"props":1061,"children":1063},{"id":1062},"situation-specific-approaches",[1064],{"type":46,"value":1065},"Situation-Specific Approaches",{"type":41,"tag":53,"props":1067,"children":1068},{},[1069],{"type":41,"tag":163,"props":1070,"children":1071},{},[1072],{"type":46,"value":1073},"Answering a product question:",{"type":41,"tag":98,"props":1075,"children":1076},{},[1077,1082,1087,1092],{"type":41,"tag":102,"props":1078,"children":1079},{},[1080],{"type":46,"value":1081},"Lead with the direct answer",{"type":41,"tag":102,"props":1083,"children":1084},{},[1085],{"type":46,"value":1086},"Provide relevant documentation links",{"type":41,"tag":102,"props":1088,"children":1089},{},[1090],{"type":46,"value":1091},"Offer to connect them with the right resource if needed",{"type":41,"tag":102,"props":1093,"children":1094},{},[1095],{"type":46,"value":1096},"If you don't know the answer: say so honestly, commit to finding out, give a timeline",{"type":41,"tag":53,"props":1098,"children":1099},{},[1100],{"type":41,"tag":163,"props":1101,"children":1102},{},[1103],{"type":46,"value":1104},"Responding to an issue or bug:",{"type":41,"tag":98,"props":1106,"children":1107},{},[1108,1113,1118,1123,1128],{"type":41,"tag":102,"props":1109,"children":1110},{},[1111],{"type":46,"value":1112},"Acknowledge the impact on their work",{"type":41,"tag":102,"props":1114,"children":1115},{},[1116],{"type":46,"value":1117},"State what you know about the issue and its status",{"type":41,"tag":102,"props":1119,"children":1120},{},[1121],{"type":46,"value":1122},"Provide workaround if available",{"type":41,"tag":102,"props":1124,"children":1125},{},[1126],{"type":46,"value":1127},"Set expectations for resolution timeline",{"type":41,"tag":102,"props":1129,"children":1130},{},[1131],{"type":46,"value":1132},"Commit to updates at regular intervals",{"type":41,"tag":53,"props":1134,"children":1135},{},[1136],{"type":41,"tag":163,"props":1137,"children":1138},{},[1139],{"type":46,"value":1140},"Handling an escalation:",{"type":41,"tag":98,"props":1142,"children":1143},{},[1144,1149,1154,1159,1164],{"type":41,"tag":102,"props":1145,"children":1146},{},[1147],{"type":46,"value":1148},"Acknowledge the severity and their frustration",{"type":41,"tag":102,"props":1150,"children":1151},{},[1152],{"type":46,"value":1153},"Take ownership (no deflecting or excuse-making)",{"type":41,"tag":102,"props":1155,"children":1156},{},[1157],{"type":46,"value":1158},"Provide a clear action plan with timeline",{"type":41,"tag":102,"props":1160,"children":1161},{},[1162],{"type":46,"value":1163},"Identify the person accountable for resolution",{"type":41,"tag":102,"props":1165,"children":1166},{},[1167],{"type":46,"value":1168},"Offer a meeting or call if appropriate for the severity",{"type":41,"tag":53,"props":1170,"children":1171},{},[1172],{"type":41,"tag":163,"props":1173,"children":1174},{},[1175],{"type":46,"value":1176},"Delivering bad news (feature sunset, delay, can't-fix):",{"type":41,"tag":98,"props":1178,"children":1179},{},[1180,1185,1190,1195,1200],{"type":41,"tag":102,"props":1181,"children":1182},{},[1183],{"type":46,"value":1184},"Be direct — don't bury the news",{"type":41,"tag":102,"props":1186,"children":1187},{},[1188],{"type":46,"value":1189},"Explain the reasoning honestly",{"type":41,"tag":102,"props":1191,"children":1192},{},[1193],{"type":46,"value":1194},"Acknowledge the impact on them specifically",{"type":41,"tag":102,"props":1196,"children":1197},{},[1198],{"type":46,"value":1199},"Offer alternatives or mitigation",{"type":41,"tag":102,"props":1201,"children":1202},{},[1203],{"type":46,"value":1204},"Provide a clear path forward",{"type":41,"tag":53,"props":1206,"children":1207},{},[1208],{"type":41,"tag":163,"props":1209,"children":1210},{},[1211],{"type":46,"value":1212},"Sharing good news (feature launch, milestone, recognition):",{"type":41,"tag":98,"props":1214,"children":1215},{},[1216,1221,1226,1231],{"type":41,"tag":102,"props":1217,"children":1218},{},[1219],{"type":46,"value":1220},"Lead with the positive outcome",{"type":41,"tag":102,"props":1222,"children":1223},{},[1224],{"type":46,"value":1225},"Connect it to their specific goals or use case",{"type":41,"tag":102,"props":1227,"children":1228},{},[1229],{"type":46,"value":1230},"Suggest next steps to capitalize on the good news",{"type":41,"tag":102,"props":1232,"children":1233},{},[1234],{"type":46,"value":1235},"Express genuine enthusiasm",{"type":41,"tag":53,"props":1237,"children":1238},{},[1239],{"type":41,"tag":163,"props":1240,"children":1241},{},[1242],{"type":46,"value":1243},"Declining a request (feature request, discount, exception):",{"type":41,"tag":98,"props":1245,"children":1246},{},[1247,1252,1257,1262,1267],{"type":41,"tag":102,"props":1248,"children":1249},{},[1250],{"type":46,"value":1251},"Acknowledge the request and its reasoning",{"type":41,"tag":102,"props":1253,"children":1254},{},[1255],{"type":46,"value":1256},"Be honest about the decision",{"type":41,"tag":102,"props":1258,"children":1259},{},[1260],{"type":46,"value":1261},"Explain the why without being dismissive",{"type":41,"tag":102,"props":1263,"children":1264},{},[1265],{"type":46,"value":1266},"Offer alternatives when possible",{"type":41,"tag":102,"props":1268,"children":1269},{},[1270],{"type":46,"value":1271},"Leave the door open for future conversation",{"type":41,"tag":73,"props":1273,"children":1275},{"id":1274},"response-templates-for-common-scenarios",[1276],{"type":46,"value":1277},"Response Templates for Common Scenarios",{"type":41,"tag":145,"props":1279,"children":1281},{"id":1280},"acknowledging-a-bug-report",[1282],{"type":46,"value":1283},"Acknowledging a Bug Report",{"type":41,"tag":80,"props":1285,"children":1288},{"className":1286,"code":1287,"language":46},[83],"Hi [Name],\n\nThank you for reporting this — I can see how [specific impact] would be\nfrustrating for your team.\n\nI've confirmed the issue and escalated it to our engineering team as a\n[priority level]. Here's what we know so far:\n- [What's happening]\n- [What's causing it, if known]\n- [Workaround, if available]\n\nI'll update you by [specific date\u002Ftime] with a resolution timeline.\nIn the meantime, [workaround details if applicable].\n\nLet me know if you have any questions or if this is impacting you in\nother ways I should know about.\n\nBest,\n[Your name]\n",[1289],{"type":41,"tag":87,"props":1290,"children":1291},{"__ignoreMap":89},[1292],{"type":46,"value":1287},{"type":41,"tag":145,"props":1294,"children":1296},{"id":1295},"acknowledging-a-billing-or-account-issue",[1297],{"type":46,"value":1298},"Acknowledging a Billing or Account Issue",{"type":41,"tag":80,"props":1300,"children":1303},{"className":1301,"code":1302,"language":46},[83],"Hi [Name],\n\nThank you for reaching out about this — I understand billing issues\nneed prompt attention, and I want to make sure this gets resolved\nquickly.\n\nI've looked into your account and here's what I'm seeing:\n- [What happened — clear factual explanation]\n- [Impact on their account — charges, access, etc.]\n\nHere's what I'm doing to fix this:\n- [Action 1 — with timeline]\n- [Action 2 — if applicable]\n\n[If resolution is immediate: \"This has been corrected and you should\nsee the change reflected within [timeframe].\"]\n[If needs investigation: \"I'm escalating this to our billing team\nand will have an update for you by [specific date].\"]\n\nI'm sorry for the inconvenience. Let me know if you have any\nquestions about your account.\n\nBest,\n[Your name]\n",[1304],{"type":41,"tag":87,"props":1305,"children":1306},{"__ignoreMap":89},[1307],{"type":46,"value":1302},{"type":41,"tag":145,"props":1309,"children":1311},{"id":1310},"responding-to-a-feature-request-you-wont-build",[1312],{"type":46,"value":1313},"Responding to a Feature Request You Won't Build",{"type":41,"tag":80,"props":1315,"children":1318},{"className":1316,"code":1317,"language":46},[83],"Hi [Name],\n\nThank you for sharing this request — I can see why [capability] would\nbe valuable for [their use case].\n\nI discussed this with our product team, and this isn't something we're\nplanning to build in the near term. The primary reason is [honest,\nrespectful explanation — e.g., it serves a narrow use case, it conflicts\nwith our architecture direction, etc.].\n\nThat said, I want to make sure you can accomplish your goal. Here are\nsome alternatives:\n- [Alternative approach 1]\n- [Alternative approach 2]\n- [Integration or workaround if applicable]\n\nI've also documented your request in our feedback system, and if our\ndirection changes, I'll let you know.\n\nWould any of these alternatives work for your team? Happy to dig\ndeeper into any of them.\n\nBest,\n[Your name]\n",[1319],{"type":41,"tag":87,"props":1320,"children":1321},{"__ignoreMap":89},[1322],{"type":46,"value":1317},{"type":41,"tag":145,"props":1324,"children":1326},{"id":1325},"outage-or-incident-communication",[1327],{"type":46,"value":1328},"Outage or Incident Communication",{"type":41,"tag":80,"props":1330,"children":1333},{"className":1331,"code":1332,"language":46},[83],"Hi [Name],\n\nI wanted to reach out directly to let you know about an issue affecting\n[service\u002Ffeature] that I know your team relies on.\n\n**What happened:** [Clear, non-technical explanation]\n**Impact:** [How it affects them specifically]\n**Status:** [Current status — investigating \u002F identified \u002F fixing \u002F resolved]\n**ETA for resolution:** [Specific time if known, or \"we'll update every X hours\"]\n\n[If applicable: \"In the meantime, you can [workaround].\"]\n\nI'm personally tracking this and will update you as soon as we have a\nresolution. You can also check [status page URL] for real-time updates.\n\nI'm sorry for the disruption to your team's work. We take this seriously\nand [what you're doing to prevent recurrence if known].\n\n[Your name]\n",[1334],{"type":41,"tag":87,"props":1335,"children":1336},{"__ignoreMap":89},[1337],{"type":46,"value":1332},{"type":41,"tag":145,"props":1339,"children":1341},{"id":1340},"following-up-after-silence",[1342],{"type":46,"value":1343},"Following Up After Silence",{"type":41,"tag":80,"props":1345,"children":1348},{"className":1346,"code":1347,"language":46},[83],"Hi [Name],\n\nI wanted to check in — I sent over [what you sent] on [date] and\nwanted to make sure it didn't get lost in the shuffle.\n\n[Brief reminder of what you need from them or what you're offering]\n\nIf now isn't a good time, no worries — just let me know when would be\nbetter, and I'm happy to reconnect then.\n\nBest,\n[Your name]\n",[1349],{"type":41,"tag":87,"props":1350,"children":1351},{"__ignoreMap":89},[1352],{"type":46,"value":1347},{"type":41,"tag":73,"props":1354,"children":1356},{"id":1355},"follow-up-and-escalation-guidance",[1357],{"type":46,"value":1358},"Follow-up and Escalation Guidance",{"type":41,"tag":145,"props":1360,"children":1362},{"id":1361},"follow-up-cadence",[1363],{"type":46,"value":1364},"Follow-up Cadence",{"type":41,"tag":698,"props":1366,"children":1367},{},[1368,1383],{"type":41,"tag":702,"props":1369,"children":1370},{},[1371],{"type":41,"tag":706,"props":1372,"children":1373},{},[1374,1378],{"type":41,"tag":710,"props":1375,"children":1376},{},[1377],{"type":46,"value":714},{"type":41,"tag":710,"props":1379,"children":1380},{},[1381],{"type":46,"value":1382},"Follow-up Timing",{"type":41,"tag":726,"props":1384,"children":1385},{},[1386,1399,1412,1425,1438],{"type":41,"tag":706,"props":1387,"children":1388},{},[1389,1394],{"type":41,"tag":733,"props":1390,"children":1391},{},[1392],{"type":46,"value":1393},"Unanswered question",{"type":41,"tag":733,"props":1395,"children":1396},{},[1397],{"type":46,"value":1398},"2-3 business days",{"type":41,"tag":706,"props":1400,"children":1401},{},[1402,1407],{"type":41,"tag":733,"props":1403,"children":1404},{},[1405],{"type":46,"value":1406},"Open support issue",{"type":41,"tag":733,"props":1408,"children":1409},{},[1410],{"type":46,"value":1411},"Daily until resolved for critical, 2-3 days for standard",{"type":41,"tag":706,"props":1413,"children":1414},{},[1415,1420],{"type":41,"tag":733,"props":1416,"children":1417},{},[1418],{"type":46,"value":1419},"Post-meeting action items",{"type":41,"tag":733,"props":1421,"children":1422},{},[1423],{"type":46,"value":1424},"Within 24 hours (send notes), then check at deadline",{"type":41,"tag":706,"props":1426,"children":1427},{},[1428,1433],{"type":41,"tag":733,"props":1429,"children":1430},{},[1431],{"type":46,"value":1432},"General check-in",{"type":41,"tag":733,"props":1434,"children":1435},{},[1436],{"type":46,"value":1437},"As needed for ongoing issues",{"type":41,"tag":706,"props":1439,"children":1440},{},[1441,1446],{"type":41,"tag":733,"props":1442,"children":1443},{},[1444],{"type":46,"value":1445},"After delivering bad news",{"type":41,"tag":733,"props":1447,"children":1448},{},[1449],{"type":46,"value":1450},"1 week to check on impact and sentiment",{"type":41,"tag":145,"props":1452,"children":1454},{"id":1453},"when-to-escalate",[1455],{"type":46,"value":1456},"When to Escalate",{"type":41,"tag":53,"props":1458,"children":1459},{},[1460],{"type":41,"tag":163,"props":1461,"children":1462},{},[1463],{"type":46,"value":1464},"Escalate to your manager when:",{"type":41,"tag":98,"props":1466,"children":1467},{},[1468,1473,1478,1483,1488],{"type":41,"tag":102,"props":1469,"children":1470},{},[1471],{"type":46,"value":1472},"Customer threatens to cancel or significantly downsell",{"type":41,"tag":102,"props":1474,"children":1475},{},[1476],{"type":46,"value":1477},"Customer requests exception to policy you can't authorize",{"type":41,"tag":102,"props":1479,"children":1480},{},[1481],{"type":46,"value":1482},"An issue has been unresolved for longer than SLA allows",{"type":41,"tag":102,"props":1484,"children":1485},{},[1486],{"type":46,"value":1487},"Customer requests direct contact with leadership",{"type":41,"tag":102,"props":1489,"children":1490},{},[1491],{"type":46,"value":1492},"You've made an error that needs senior involvement to resolve",{"type":41,"tag":53,"props":1494,"children":1495},{},[1496],{"type":41,"tag":163,"props":1497,"children":1498},{},[1499],{"type":46,"value":1500},"Escalate to product\u002Fengineering when:",{"type":41,"tag":98,"props":1502,"children":1503},{},[1504,1509,1514,1519],{"type":41,"tag":102,"props":1505,"children":1506},{},[1507],{"type":46,"value":1508},"Bug is critical and blocking the customer's business",{"type":41,"tag":102,"props":1510,"children":1511},{},[1512],{"type":46,"value":1513},"Feature gap is causing a competitive loss",{"type":41,"tag":102,"props":1515,"children":1516},{},[1517],{"type":46,"value":1518},"Customer has unique technical requirements beyond standard support",{"type":41,"tag":102,"props":1520,"children":1521},{},[1522],{"type":46,"value":1523},"Integration issues require engineering investigation",{"type":41,"tag":53,"props":1525,"children":1526},{},[1527],{"type":41,"tag":163,"props":1528,"children":1529},{},[1530],{"type":46,"value":1531},"Escalation format:",{"type":41,"tag":80,"props":1533,"children":1536},{"className":1534,"code":1535,"language":46},[83],"ESCALATION: [Customer Name] — [One-line summary]\n\nUrgency: [Critical \u002F High \u002F Medium]\nCustomer impact: [What's broken for them]\nHistory: [Brief background — 2-3 sentences]\nWhat I've tried: [Actions taken so far]\nWhat I need: [Specific help or decision needed]\nDeadline: [When this needs to be resolved by]\n",[1537],{"type":41,"tag":87,"props":1538,"children":1539},{"__ignoreMap":89},[1540],{"type":46,"value":1535},{"items":1542,"total":1725},[1543,1564,1578,1590,1609,1622,1643,1663,1673,1688,1696,1709],{"slug":1544,"name":1544,"fn":1545,"description":1546,"org":1547,"tags":1548,"stars":1561,"repoUrl":1562,"updatedAt":1563},"algorithmic-art","create algorithmic art with p5.js","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1549,1552,1555,1558],{"name":1550,"slug":1551,"type":16},"Creative","creative",{"name":1553,"slug":1554,"type":16},"Design","design",{"name":1556,"slug":1557,"type":16},"Generative Art","generative-art",{"name":1559,"slug":1560,"type":16},"JavaScript","javascript",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-04-06T17:56:15.455818",{"slug":1565,"name":1565,"fn":1566,"description":1567,"org":1568,"tags":1569,"stars":1561,"repoUrl":1562,"updatedAt":1577},"brand-guidelines","apply Anthropic brand colors and typography","Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1570,1573,1574],{"name":1571,"slug":1572,"type":16},"Branding","branding",{"name":1553,"slug":1554,"type":16},{"name":1575,"slug":1576,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":1579,"name":1579,"fn":1580,"description":1581,"org":1582,"tags":1583,"stars":1561,"repoUrl":1562,"updatedAt":1589},"canvas-design","create posters and visual art as PNG or PDF","Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1584,1585,1586],{"name":1550,"slug":1551,"type":16},{"name":1553,"slug":1554,"type":16},{"name":1587,"slug":1588,"type":16},"PDF","pdf","2026-04-06T17:56:03.794732",{"slug":1591,"name":1591,"fn":1592,"description":1593,"org":1594,"tags":1595,"stars":1561,"repoUrl":1562,"updatedAt":1608},"claude-api","build apps with the Claude API","Reference for the Claude API \u002F Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.\nTRIGGER — read BEFORE opening the target file; don't skip because it \"looks like a one-liner\" — whenever: the prompt names Claude\u002FAnthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing\u002Fmodel choice\u002Flimits\u002Fcaching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent\u002FMCP\u002Ftool-definition\u002Fmulti-agent\u002FRAG\u002FLLM-judge\u002Fcomputer-use; generate\u002Fsummarize\u002Fextract\u002Fclassify\u002Frewrite\u002Fconverse over NL; debugging refusals\u002Fcutoffs\u002Fstreaming\u002Ftool-calls\u002Ftokens).\nSKIP only when another provider is being worked on (overrides all triggers): OpenAI\u002FGPT\u002FGemini\u002FLlama\u002FMistral\u002FCohere\u002FOllama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1596,1599,1600,1603,1605],{"name":1597,"slug":1598,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":1601,"slug":1602,"type":16},"Anthropic SDK","anthropic-sdk",{"name":1604,"slug":1591,"type":16},"Claude API",{"name":1606,"slug":1607,"type":16},"LLM","llm","2026-07-28T05:36:08.213335",{"slug":1610,"name":1610,"fn":1611,"description":1612,"org":1613,"tags":1614,"stars":1561,"repoUrl":1562,"updatedAt":1621},"doc-coauthoring","co-author documentation and technical specs","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1615,1618],{"name":1616,"slug":1617,"type":16},"Documentation","documentation",{"name":1619,"slug":1620,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":1623,"name":1623,"fn":1624,"description":1625,"org":1626,"tags":1627,"stars":1561,"repoUrl":1562,"updatedAt":1642},"docx","create and edit Word documents","Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1628,1631,1633,1636,1639],{"name":1629,"slug":1630,"type":16},"Documents","documents",{"name":1632,"slug":1623,"type":16},"DOCX",{"name":1634,"slug":1635,"type":16},"Office","office",{"name":1637,"slug":1638,"type":16},"Templates","templates",{"name":1640,"slug":1641,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":1644,"name":1644,"fn":1645,"description":1646,"org":1647,"tags":1648,"stars":1561,"repoUrl":1562,"updatedAt":1662},"frontend-design","design production-grade frontend interfaces","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1649,1650,1653,1656,1659],{"name":1553,"slug":1554,"type":16},{"name":1651,"slug":1652,"type":16},"Frontend","frontend",{"name":1654,"slug":1655,"type":16},"React","react",{"name":1657,"slug":1658,"type":16},"Tailwind CSS","tailwind-css",{"name":1660,"slug":1661,"type":16},"UI Components","ui-components","2026-04-06T17:56:16.723469",{"slug":1664,"name":1664,"fn":1665,"description":1666,"org":1667,"tags":1668,"stars":1561,"repoUrl":1562,"updatedAt":1672},"internal-comms","write internal company communications","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1669,1670,1671],{"name":21,"slug":22,"type":16},{"name":1637,"slug":1638,"type":16},{"name":14,"slug":15,"type":16},"2026-04-06T17:56:20.695522",{"slug":1674,"name":1674,"fn":1675,"description":1676,"org":1677,"tags":1678,"stars":1561,"repoUrl":1562,"updatedAt":1687},"mcp-builder","build MCP servers","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node\u002FTypeScript (MCP SDK).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1679,1680,1683,1684],{"name":1597,"slug":1598,"type":16},{"name":1681,"slug":1682,"type":16},"API Development","api-development",{"name":1606,"slug":1607,"type":16},{"name":1685,"slug":1686,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":1588,"name":1588,"fn":1689,"description":1690,"org":1691,"tags":1692,"stars":1561,"repoUrl":1562,"updatedAt":1695},"read edit and manipulate PDF files","Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text\u002Ftables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting\u002Fdecrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1693,1694],{"name":1629,"slug":1630,"type":16},{"name":1587,"slug":1588,"type":16},"2026-04-06T17:56:02.483316",{"slug":1697,"name":1697,"fn":1698,"description":1699,"org":1700,"tags":1701,"stars":1561,"repoUrl":1562,"updatedAt":1708},"pptx","create and edit PowerPoint presentations","Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1702,1705],{"name":1703,"slug":1704,"type":16},"PowerPoint","powerpoint",{"name":1706,"slug":1707,"type":16},"Presentations","presentations","2026-07-18T05:16:24.1471",{"slug":1710,"name":1710,"fn":1711,"description":1712,"org":1713,"tags":1714,"stars":1561,"repoUrl":1562,"updatedAt":1724},"skill-creator","create and optimize agent skills","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1715,1716,1717,1720,1723],{"name":1597,"slug":1598,"type":16},{"name":1616,"slug":1617,"type":16},{"name":1718,"slug":1719,"type":16},"Evals","evals",{"name":1721,"slug":1722,"type":16},"Performance","performance",{"name":1619,"slug":1620,"type":16},"2026-04-19T06:45:40.804",490,{"items":1727,"total":1834},[1728,1742,1758,1774,1790,1809,1821],{"slug":1729,"name":1729,"fn":1730,"description":1731,"org":1732,"tags":1733,"stars":23,"repoUrl":24,"updatedAt":1741},"accessibility-review","run WCAG accessibility audits","Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with \"audit accessibility\", \"check a11y\", \"is this accessible?\", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1734,1737,1738],{"name":1735,"slug":1736,"type":16},"Accessibility","accessibility",{"name":1553,"slug":1554,"type":16},{"name":1739,"slug":1740,"type":16},"WCAG","wcag","2026-04-06T17:58:05.682394",{"slug":1743,"name":1743,"fn":1744,"description":1745,"org":1746,"tags":1747,"stars":23,"repoUrl":24,"updatedAt":1757},"account-research","research accounts for sales intel","Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with \"research [company]\", \"look up [person]\", \"intel on [prospect]\", \"who is [name] at [company]\", or \"tell me about [company]\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1748,1751,1754],{"name":1749,"slug":1750,"type":16},"CRM","crm",{"name":1752,"slug":1753,"type":16},"Research","research",{"name":1755,"slug":1756,"type":16},"Sales","sales","2026-04-06T17:56:41.410418",{"slug":1759,"name":1759,"fn":1760,"description":1761,"org":1762,"tags":1763,"stars":23,"repoUrl":24,"updatedAt":1773},"analyze","answer data questions and run analyses","Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1764,1767,1770],{"name":1765,"slug":1766,"type":16},"Analytics","analytics",{"name":1768,"slug":1769,"type":16},"Data Analysis","data-analysis",{"name":1771,"slug":1772,"type":16},"SQL","sql","2026-04-06T17:57:21.593647",{"slug":1775,"name":1775,"fn":1776,"description":1777,"org":1778,"tags":1779,"stars":23,"repoUrl":24,"updatedAt":1789},"architecture","create and evaluate architecture decision records","Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1780,1783,1785,1786],{"name":1781,"slug":1782,"type":16},"ADR","adr",{"name":1784,"slug":1775,"type":16},"Architecture",{"name":1616,"slug":1617,"type":16},{"name":1787,"slug":1788,"type":16},"Engineering","engineering","2026-04-06T17:57:49.26444",{"slug":1791,"name":1791,"fn":1792,"description":1793,"org":1794,"tags":1795,"stars":23,"repoUrl":24,"updatedAt":1808},"audit-support","support SOX 404 control testing","Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1796,1799,1802,1805],{"name":1797,"slug":1798,"type":16},"Audit","audit",{"name":1800,"slug":1801,"type":16},"Finance","finance",{"name":1803,"slug":1804,"type":16},"Regulatory Compliance","regulatory-compliance",{"name":1806,"slug":1807,"type":16},"SOX","sox","2026-04-06T17:57:36.714815",{"slug":1810,"name":1810,"fn":1811,"description":1812,"org":1813,"tags":1814,"stars":23,"repoUrl":24,"updatedAt":1820},"brand-review","review content against brand voice","Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before\u002Fafter fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1815,1816,1819],{"name":1571,"slug":1572,"type":16},{"name":1817,"slug":1818,"type":16},"Marketing","marketing",{"name":14,"slug":15,"type":16},"2026-04-06T17:58:19.548331",{"slug":1822,"name":1822,"fn":1823,"description":1824,"org":1825,"tags":1826,"stars":23,"repoUrl":24,"updatedAt":1833},"brand-voice-enforcement","enforce brand voice in content","This skill applies brand guidelines to content creation. It should be used when the user asks to \"write an email\", \"draft a proposal\", \"create a pitch deck\", \"write a LinkedIn post\", \"draft a presentation\", \"write a Slack message\", \"draft sales content\", or any content creation request where brand voice should be applied. Also triggers on \"on-brand\", \"brand voice\", \"enforce voice\", \"apply brand guidelines\", \"brand-aligned content\", \"write in our voice\", \"use our brand tone\", \"make this sound like us\", \"rewrite this in our tone\", or \"this doesn't sound on-brand\". Not for generating guidelines from scratch (use guideline-generation) or discovering brand materials (use discover-brand).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1827,1828,1829,1832],{"name":1571,"slug":1572,"type":16},{"name":21,"slug":22,"type":16},{"name":1830,"slug":1831,"type":16},"Content Creation","content-creation",{"name":14,"slug":15,"type":16},"2026-04-06T18:00:23.528956",200]