[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-customer-escalation":3,"mdc--jjfe1i-key":34,"related-repo-anthropic-customer-escalation":1207,"related-org-anthropic-customer-escalation":1324},{"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},"customer-escalation","package customer escalations with context","Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.",{"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},"Customer Support","customer-support","tag",{"name":18,"slug":19,"type":16},"Escalation","escalation",{"name":21,"slug":22,"type":16},"Communications","communications",22885,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","2026-04-06T17:58:57.527135",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\u002Fcustomer-escalation","---\nname: customer-escalation\ndescription: Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.\nargument-hint: \"\u003Cissue summary> [customer name]\"\n---\n\n# \u002Fcustomer-escalation\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nPackage a support issue into a structured escalation brief for engineering, product, or leadership. Gathers context, structures reproduction steps, assesses business impact, and identifies the right escalation target.\n\n## Usage\n\n```\n\u002Fcustomer-escalation \u003Cissue description> [customer name or account]\n```\n\nExamples:\n- `\u002Fcustomer-escalation API returning 500 errors intermittently for Acme Corp`\n- `\u002Fcustomer-escalation Data export is missing rows — 3 customers reported this week`\n- `\u002Fcustomer-escalation SSO login loop affecting all Enterprise customers`\n- `\u002Fcustomer-escalation Customer threatening to churn over missing audit log feature`\n\n## Workflow\n\n### 1. Understand the Issue\n\nParse the input and determine:\n\n- **What's broken or needed**: The core technical or product issue\n- **Who's affected**: Specific customer(s), segment, or all users\n- **How long**: When did this start? How long has the customer been waiting?\n- **What's been tried**: Any troubleshooting or workarounds attempted\n- **Why escalate now**: What makes this need attention beyond normal support\n\nUse the \"When to Escalate vs. Handle in Support\" criteria below to confirm this warrants escalation.\n\n### 2. Gather Context\n\nPull together relevant information from available sources:\n\n- **~~support platform**: Related tickets, timeline of communications, previous troubleshooting\n- **~~CRM** (if connected): Account details, key contacts, previous escalations\n- **~~chat**: Internal discussions about this issue, similar reports from other customers\n- **~~project tracker** (if connected): Related bug reports or feature requests, engineering status\n- **~~knowledge base**: Known issues or workarounds, relevant documentation\n\n### 3. Assess Business Impact\n\nUsing the impact dimensions below, quantify:\n\n- **Breadth**: How many customers\u002Fusers affected? Growing?\n- **Depth**: Blocked vs. inconvenienced?\n- **Duration**: How long has this been going on?\n- **Revenue**: ARR at risk? Pending deals affected?\n- **Time pressure**: Hard deadline?\n\n### 4. Determine Escalation Target\n\nUsing the escalation tiers below, identify the right target: L2 Support, Engineering, Product, Security, or Leadership.\n\n### 5. Structure Reproduction Steps (for bugs)\n\nIf the issue is a bug, follow the reproduction step best practices below to document clear repro steps with environment details and evidence.\n\n### 6. Generate Escalation Brief\n\n```\n## ESCALATION: [One-line summary]\n\n**Severity:** [Critical \u002F High \u002F Medium]\n**Target team:** [Engineering \u002F Product \u002F Security \u002F Leadership]\n**Reported by:** [Your name\u002Fteam]\n**Date:** [Today's date]\n\n### Impact\n- **Customers affected:** [Who and how many]\n- **Workflow impact:** [What they can't do]\n- **Revenue at risk:** [If applicable]\n- **Time in queue:** [How long this has been an issue]\n\n### Issue Description\n[Clear, concise description of the problem — 3-5 sentences]\n\n### What's Been Tried\n1. [Troubleshooting step and result]\n2. [Troubleshooting step and result]\n3. [Troubleshooting step and result]\n\n### Reproduction Steps\n[If applicable — follow the format below]\n1. [Step]\n2. [Step]\n3. [Step]\nExpected: [X]\nActual: [Y]\nEnvironment: [Details]\n\n### Customer Communication\n- **Last update to customer:** [Date and what was communicated]\n- **Customer expectation:** [What they're expecting and by when]\n- **Escalation risk:** [Will they escalate further if not resolved by X?]\n\n### What's Needed\n- [Specific ask — \"investigate root cause\", \"prioritize fix\",\n  \"make product decision on X\", \"approve exception for Y\"]\n- **Deadline:** [When this needs resolution or an update]\n\n### Supporting Context\n- [Related tickets or links]\n- [Internal discussion threads]\n- [Documentation or logs]\n```\n\n### 7. Offer Next Steps\n\nAfter generating the escalation:\n- \"Want me to post this in a ~~chat channel for the target team?\"\n- \"Should I update the customer with an interim response?\"\n- \"Want me to set a follow-up reminder to check on this?\"\n- \"Should I draft a customer-facing update with the current status?\"\n\n---\n\n## When to Escalate vs. Handle in Support\n\n### Handle in Support When:\n- The issue has a documented solution or known workaround\n- It's a configuration or setup issue you can resolve\n- The customer needs guidance or training, not a fix\n- The issue is a known limitation with a documented alternative\n- Previous similar tickets were resolved at the support level\n\n### Escalate When:\n- **Technical**: Bug confirmed and needs a code fix, infrastructure investigation needed, data corruption or loss\n- **Complexity**: Issue is beyond support's ability to diagnose, requires access support doesn't have, involves custom implementation\n- **Impact**: Multiple customers affected, production system down, data integrity at risk, security concern\n- **Business**: High-value customer at risk, SLA breach imminent or occurred, customer requesting executive involvement\n- **Time**: Issue has been open beyond SLA, customer has been waiting unreasonably long, normal support channels aren't progressing\n- **Pattern**: Same issue reported by 3+ customers, recurring issue that was supposedly fixed, increasing severity over time\n\n## Escalation Tiers\n\n### L1 → L2 (Support Escalation)\n**From:** Frontline support\n**To:** Senior support \u002F technical support specialists\n**When:** Issue requires deeper investigation, specialized product knowledge, or advanced troubleshooting\n**What to include:** Ticket summary, steps already tried, customer context\n\n### L2 → Engineering\n**From:** Senior support\n**To:** Engineering team (relevant product area)\n**When:** Confirmed bug, infrastructure issue, needs code change, requires system-level investigation\n**What to include:** Full reproduction steps, environment details, logs or error messages, business impact, customer timeline\n\n### L2 → Product\n**From:** Senior support\n**To:** Product management\n**When:** Feature gap causing customer pain, design decision needed, workflow doesn't match customer expectations, competing customer needs require prioritization\n**What to include:** Customer use case, business impact, frequency of request, competitive pressure (if known)\n\n### Any → Security\n**From:** Any support tier\n**To:** Security team\n**When:** Potential data exposure, unauthorized access, vulnerability report, compliance concern\n**What to include:** What was observed, who\u002Fwhat is potentially affected, immediate containment steps taken, urgency assessment\n**Note:** Security escalations bypass normal tier progression — escalate immediately regardless of your level\n\n### Any → Leadership\n**From:** Any tier (usually L2 or manager)\n**To:** Support leadership, executive team\n**When:** High-revenue customer threatening churn, SLA breach on critical account, cross-functional decision needed, exception to policy required, PR or legal risk\n**What to include:** Full business context, revenue at risk, what's been tried, specific decision or action needed, deadline\n\n## Business Impact Assessment\n\nWhen escalating, quantify impact where possible:\n\n### Impact Dimensions\n\n| Dimension | Questions to Answer |\n|-----------|-------------------|\n| **Breadth** | How many customers\u002Fusers are affected? Is it growing? |\n| **Depth** | How severely are they impacted? Blocked vs. inconvenienced? |\n| **Duration** | How long has this been going on? How long until it's critical? |\n| **Revenue** | What's the ARR at risk? Are there pending deals affected? |\n| **Reputation** | Could this become public? Is it a reference customer? |\n| **Contractual** | Are SLAs being breached? Are there contractual obligations? |\n\n### Severity Shorthand\n\n- **Critical**: Production down, data at risk, security breach, or multiple high-value customers affected. Needs immediate attention.\n- **High**: Major functionality broken, key customer blocked, SLA at risk. Needs same-day attention.\n- **Medium**: Significant issue with workaround, important but not urgent business impact. Needs attention this week.\n\n## Writing Reproduction Steps\n\nGood reproduction steps are the single most valuable thing in a bug escalation. Follow these practices:\n\n1. **Start from a clean state**: Describe the starting point (account type, configuration, permissions)\n2. **Be specific**: \"Click the Export button in the top-right of the Dashboard page\" not \"try to export\"\n3. **Include exact values**: Use specific inputs, dates, IDs — not \"enter some data\"\n4. **Note the environment**: Browser, OS, account type, feature flags, plan level\n5. **Capture the frequency**: Always reproducible? Intermittent? Only under certain conditions?\n6. **Include evidence**: Screenshots, error messages (exact text), network logs, console output\n7. **Note what you've ruled out**: \"Tested in Chrome and Firefox — same behavior\" \"Not account-specific — reproduced on test account\"\n\n## Follow-up Cadence After Escalation\n\nDon't escalate and forget. Maintain ownership of the customer relationship.\n\n| Severity | Internal Follow-up | Customer Update |\n|----------|-------------------|-----------------|\n| **Critical** | Every 2 hours | Every 2-4 hours (or per SLA) |\n| **High** | Every 4 hours | Every 4-8 hours |\n| **Medium** | Daily | Every 1-2 business days |\n\n### Follow-up Actions\n- Check with the receiving team for progress\n- Update the customer even if there's no new information (\"We're still investigating — here's what we know so far\")\n- Adjust severity if the situation changes (better or worse)\n- Document all updates in the ticket for audit trail\n- Close the loop when resolved: confirm with customer, update internal tracking, capture learnings\n\n## De-escalation\n\nNot every escalation stays escalated. De-escalate when:\n- Root cause is found and it's a support-resolvable issue\n- A workaround is found that unblocks the customer\n- The issue resolves itself (but still document root cause)\n- New information changes the severity assessment\n\nWhen de-escalating:\n- Notify the team you escalated to\n- Update the ticket with the resolution\n- Inform the customer of the resolution\n- Document what was learned for future reference\n\n## Escalation Best Practices\n\n1. Always quantify impact — vague escalations get deprioritized\n2. Include reproduction steps for bugs — this is the #1 thing engineering needs\n3. Be clear about what you need — \"investigate\" vs. \"fix\" vs. \"decide\" are different asks\n4. Set and communicate a deadline — urgency without a deadline is ambiguous\n5. Maintain ownership of the customer relationship even after escalating the technical issue\n6. Follow up proactively — don't wait for the receiving team to come to you\n7. Document everything — the escalation trail is valuable for pattern detection and process improvement\n",{"data":35,"body":37},{"name":4,"description":6,"argument-hint":36},"\u003Cissue summary> [customer name]",{"type":38,"children":39},"root",[40,48,67,72,79,92,97,138,144,151,156,210,215,221,226,279,285,290,343,349,354,360,365,371,380,386,391,414,418,424,430,458,464,527,533,539,570,576,603,609,635,641,675,681,708,714,719,725,845,851,884,890,895,969,975,980,1067,1073,1101,1107,1112,1135,1140,1163,1169],{"type":41,"tag":42,"props":43,"children":44},"element","h1",{"id":4},[45],{"type":46,"value":47},"text","\u002Fcustomer-escalation",{"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},"Package a support issue into a structured escalation brief for engineering, product, or leadership. Gathers context, structures reproduction steps, assesses business impact, and identifies the right escalation target.",{"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","\u002Fcustomer-escalation \u003Cissue description> [customer name or account]\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},"\u002Fcustomer-escalation API returning 500 errors intermittently for Acme Corp",{"type":41,"tag":102,"props":112,"children":113},{},[114],{"type":41,"tag":87,"props":115,"children":117},{"className":116},[],[118],{"type":46,"value":119},"\u002Fcustomer-escalation Data export is missing rows — 3 customers reported this week",{"type":41,"tag":102,"props":121,"children":122},{},[123],{"type":41,"tag":87,"props":124,"children":126},{"className":125},[],[127],{"type":46,"value":128},"\u002Fcustomer-escalation SSO login loop affecting all Enterprise customers",{"type":41,"tag":102,"props":130,"children":131},{},[132],{"type":41,"tag":87,"props":133,"children":135},{"className":134},[],[136],{"type":46,"value":137},"\u002Fcustomer-escalation Customer threatening to churn over missing audit log feature",{"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-issue",[149],{"type":46,"value":150},"1. Understand the Issue",{"type":41,"tag":53,"props":152,"children":153},{},[154],{"type":46,"value":155},"Parse the input and determine:",{"type":41,"tag":98,"props":157,"children":158},{},[159,170,180,190,200],{"type":41,"tag":102,"props":160,"children":161},{},[162,168],{"type":41,"tag":163,"props":164,"children":165},"strong",{},[166],{"type":46,"value":167},"What's broken or needed",{"type":46,"value":169},": The core technical or product issue",{"type":41,"tag":102,"props":171,"children":172},{},[173,178],{"type":41,"tag":163,"props":174,"children":175},{},[176],{"type":46,"value":177},"Who's affected",{"type":46,"value":179},": Specific customer(s), segment, or all users",{"type":41,"tag":102,"props":181,"children":182},{},[183,188],{"type":41,"tag":163,"props":184,"children":185},{},[186],{"type":46,"value":187},"How long",{"type":46,"value":189},": When did this start? 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},"What's been tried",{"type":46,"value":199},": Any troubleshooting or workarounds attempted",{"type":41,"tag":102,"props":201,"children":202},{},[203,208],{"type":41,"tag":163,"props":204,"children":205},{},[206],{"type":46,"value":207},"Why escalate now",{"type":46,"value":209},": What makes this need attention beyond normal support",{"type":41,"tag":53,"props":211,"children":212},{},[213],{"type":46,"value":214},"Use the \"When to Escalate vs. Handle in Support\" criteria below to confirm this warrants escalation.",{"type":41,"tag":145,"props":216,"children":218},{"id":217},"_2-gather-context",[219],{"type":46,"value":220},"2. Gather Context",{"type":41,"tag":53,"props":222,"children":223},{},[224],{"type":46,"value":225},"Pull together relevant information from available sources:",{"type":41,"tag":98,"props":227,"children":228},{},[229,239,249,259,269],{"type":41,"tag":102,"props":230,"children":231},{},[232,237],{"type":41,"tag":163,"props":233,"children":234},{},[235],{"type":46,"value":236},"~~support platform",{"type":46,"value":238},": Related tickets, timeline of communications, previous troubleshooting",{"type":41,"tag":102,"props":240,"children":241},{},[242,247],{"type":41,"tag":163,"props":243,"children":244},{},[245],{"type":46,"value":246},"~~CRM",{"type":46,"value":248}," (if connected): Account details, key contacts, previous escalations",{"type":41,"tag":102,"props":250,"children":251},{},[252,257],{"type":41,"tag":163,"props":253,"children":254},{},[255],{"type":46,"value":256},"~~chat",{"type":46,"value":258},": Internal discussions about this issue, similar reports from other customers",{"type":41,"tag":102,"props":260,"children":261},{},[262,267],{"type":41,"tag":163,"props":263,"children":264},{},[265],{"type":46,"value":266},"~~project tracker",{"type":46,"value":268}," (if connected): Related bug reports or feature requests, engineering status",{"type":41,"tag":102,"props":270,"children":271},{},[272,277],{"type":41,"tag":163,"props":273,"children":274},{},[275],{"type":46,"value":276},"~~knowledge base",{"type":46,"value":278},": Known issues or workarounds, relevant documentation",{"type":41,"tag":145,"props":280,"children":282},{"id":281},"_3-assess-business-impact",[283],{"type":46,"value":284},"3. Assess Business Impact",{"type":41,"tag":53,"props":286,"children":287},{},[288],{"type":46,"value":289},"Using the impact dimensions below, quantify:",{"type":41,"tag":98,"props":291,"children":292},{},[293,303,313,323,333],{"type":41,"tag":102,"props":294,"children":295},{},[296,301],{"type":41,"tag":163,"props":297,"children":298},{},[299],{"type":46,"value":300},"Breadth",{"type":46,"value":302},": How many customers\u002Fusers affected? Growing?",{"type":41,"tag":102,"props":304,"children":305},{},[306,311],{"type":41,"tag":163,"props":307,"children":308},{},[309],{"type":46,"value":310},"Depth",{"type":46,"value":312},": Blocked vs. inconvenienced?",{"type":41,"tag":102,"props":314,"children":315},{},[316,321],{"type":41,"tag":163,"props":317,"children":318},{},[319],{"type":46,"value":320},"Duration",{"type":46,"value":322},": How long has this been going on?",{"type":41,"tag":102,"props":324,"children":325},{},[326,331],{"type":41,"tag":163,"props":327,"children":328},{},[329],{"type":46,"value":330},"Revenue",{"type":46,"value":332},": ARR at risk? Pending deals affected?",{"type":41,"tag":102,"props":334,"children":335},{},[336,341],{"type":41,"tag":163,"props":337,"children":338},{},[339],{"type":46,"value":340},"Time pressure",{"type":46,"value":342},": Hard deadline?",{"type":41,"tag":145,"props":344,"children":346},{"id":345},"_4-determine-escalation-target",[347],{"type":46,"value":348},"4. Determine Escalation Target",{"type":41,"tag":53,"props":350,"children":351},{},[352],{"type":46,"value":353},"Using the escalation tiers below, identify the right target: L2 Support, Engineering, Product, Security, or Leadership.",{"type":41,"tag":145,"props":355,"children":357},{"id":356},"_5-structure-reproduction-steps-for-bugs",[358],{"type":46,"value":359},"5. Structure Reproduction Steps (for bugs)",{"type":41,"tag":53,"props":361,"children":362},{},[363],{"type":46,"value":364},"If the issue is a bug, follow the reproduction step best practices below to document clear repro steps with environment details and evidence.",{"type":41,"tag":145,"props":366,"children":368},{"id":367},"_6-generate-escalation-brief",[369],{"type":46,"value":370},"6. Generate Escalation Brief",{"type":41,"tag":80,"props":372,"children":375},{"className":373,"code":374,"language":46},[83],"## ESCALATION: [One-line summary]\n\n**Severity:** [Critical \u002F High \u002F Medium]\n**Target team:** [Engineering \u002F Product \u002F Security \u002F Leadership]\n**Reported by:** [Your name\u002Fteam]\n**Date:** [Today's date]\n\n### Impact\n- **Customers affected:** [Who and how many]\n- **Workflow impact:** [What they can't do]\n- **Revenue at risk:** [If applicable]\n- **Time in queue:** [How long this has been an issue]\n\n### Issue Description\n[Clear, concise description of the problem — 3-5 sentences]\n\n### What's Been Tried\n1. [Troubleshooting step and result]\n2. [Troubleshooting step and result]\n3. [Troubleshooting step and result]\n\n### Reproduction Steps\n[If applicable — follow the format below]\n1. [Step]\n2. [Step]\n3. [Step]\nExpected: [X]\nActual: [Y]\nEnvironment: [Details]\n\n### Customer Communication\n- **Last update to customer:** [Date and what was communicated]\n- **Customer expectation:** [What they're expecting and by when]\n- **Escalation risk:** [Will they escalate further if not resolved by X?]\n\n### What's Needed\n- [Specific ask — \"investigate root cause\", \"prioritize fix\",\n  \"make product decision on X\", \"approve exception for Y\"]\n- **Deadline:** [When this needs resolution or an update]\n\n### Supporting Context\n- [Related tickets or links]\n- [Internal discussion threads]\n- [Documentation or logs]\n",[376],{"type":41,"tag":87,"props":377,"children":378},{"__ignoreMap":89},[379],{"type":46,"value":374},{"type":41,"tag":145,"props":381,"children":383},{"id":382},"_7-offer-next-steps",[384],{"type":46,"value":385},"7. Offer Next Steps",{"type":41,"tag":53,"props":387,"children":388},{},[389],{"type":46,"value":390},"After generating the escalation:",{"type":41,"tag":98,"props":392,"children":393},{},[394,399,404,409],{"type":41,"tag":102,"props":395,"children":396},{},[397],{"type":46,"value":398},"\"Want me to post this in a ~~chat channel for the target team?\"",{"type":41,"tag":102,"props":400,"children":401},{},[402],{"type":46,"value":403},"\"Should I update the customer with an interim response?\"",{"type":41,"tag":102,"props":405,"children":406},{},[407],{"type":46,"value":408},"\"Want me to set a follow-up reminder to check on this?\"",{"type":41,"tag":102,"props":410,"children":411},{},[412],{"type":46,"value":413},"\"Should I draft a customer-facing update with the current status?\"",{"type":41,"tag":415,"props":416,"children":417},"hr",{},[],{"type":41,"tag":73,"props":419,"children":421},{"id":420},"when-to-escalate-vs-handle-in-support",[422],{"type":46,"value":423},"When to Escalate vs. Handle in Support",{"type":41,"tag":145,"props":425,"children":427},{"id":426},"handle-in-support-when",[428],{"type":46,"value":429},"Handle in Support When:",{"type":41,"tag":98,"props":431,"children":432},{},[433,438,443,448,453],{"type":41,"tag":102,"props":434,"children":435},{},[436],{"type":46,"value":437},"The issue has a documented solution or known workaround",{"type":41,"tag":102,"props":439,"children":440},{},[441],{"type":46,"value":442},"It's a configuration or setup issue you can resolve",{"type":41,"tag":102,"props":444,"children":445},{},[446],{"type":46,"value":447},"The customer needs guidance or training, not a fix",{"type":41,"tag":102,"props":449,"children":450},{},[451],{"type":46,"value":452},"The issue is a known limitation with a documented alternative",{"type":41,"tag":102,"props":454,"children":455},{},[456],{"type":46,"value":457},"Previous similar tickets were resolved at the support level",{"type":41,"tag":145,"props":459,"children":461},{"id":460},"escalate-when",[462],{"type":46,"value":463},"Escalate When:",{"type":41,"tag":98,"props":465,"children":466},{},[467,477,487,497,507,517],{"type":41,"tag":102,"props":468,"children":469},{},[470,475],{"type":41,"tag":163,"props":471,"children":472},{},[473],{"type":46,"value":474},"Technical",{"type":46,"value":476},": Bug confirmed and needs a code fix, infrastructure investigation needed, data corruption or loss",{"type":41,"tag":102,"props":478,"children":479},{},[480,485],{"type":41,"tag":163,"props":481,"children":482},{},[483],{"type":46,"value":484},"Complexity",{"type":46,"value":486},": Issue is beyond support's ability to diagnose, requires access support doesn't have, involves custom implementation",{"type":41,"tag":102,"props":488,"children":489},{},[490,495],{"type":41,"tag":163,"props":491,"children":492},{},[493],{"type":46,"value":494},"Impact",{"type":46,"value":496},": Multiple customers affected, production system down, data integrity at risk, security concern",{"type":41,"tag":102,"props":498,"children":499},{},[500,505],{"type":41,"tag":163,"props":501,"children":502},{},[503],{"type":46,"value":504},"Business",{"type":46,"value":506},": High-value customer at risk, SLA breach imminent or occurred, customer requesting executive involvement",{"type":41,"tag":102,"props":508,"children":509},{},[510,515],{"type":41,"tag":163,"props":511,"children":512},{},[513],{"type":46,"value":514},"Time",{"type":46,"value":516},": Issue has been open beyond SLA, customer has been waiting unreasonably long, normal support channels aren't progressing",{"type":41,"tag":102,"props":518,"children":519},{},[520,525],{"type":41,"tag":163,"props":521,"children":522},{},[523],{"type":46,"value":524},"Pattern",{"type":46,"value":526},": Same issue reported by 3+ customers, recurring issue that was supposedly fixed, increasing severity over time",{"type":41,"tag":73,"props":528,"children":530},{"id":529},"escalation-tiers",[531],{"type":46,"value":532},"Escalation Tiers",{"type":41,"tag":145,"props":534,"children":536},{"id":535},"l1-l2-support-escalation",[537],{"type":46,"value":538},"L1 → L2 (Support Escalation)",{"type":41,"tag":53,"props":540,"children":541},{},[542,547,549,554,556,561,563,568],{"type":41,"tag":163,"props":543,"children":544},{},[545],{"type":46,"value":546},"From:",{"type":46,"value":548}," Frontline support\n",{"type":41,"tag":163,"props":550,"children":551},{},[552],{"type":46,"value":553},"To:",{"type":46,"value":555}," Senior support \u002F technical support specialists\n",{"type":41,"tag":163,"props":557,"children":558},{},[559],{"type":46,"value":560},"When:",{"type":46,"value":562}," Issue requires deeper investigation, specialized product knowledge, or advanced troubleshooting\n",{"type":41,"tag":163,"props":564,"children":565},{},[566],{"type":46,"value":567},"What to include:",{"type":46,"value":569}," Ticket summary, steps already tried, customer context",{"type":41,"tag":145,"props":571,"children":573},{"id":572},"l2-engineering",[574],{"type":46,"value":575},"L2 → Engineering",{"type":41,"tag":53,"props":577,"children":578},{},[579,583,585,589,591,595,597,601],{"type":41,"tag":163,"props":580,"children":581},{},[582],{"type":46,"value":546},{"type":46,"value":584}," Senior support\n",{"type":41,"tag":163,"props":586,"children":587},{},[588],{"type":46,"value":553},{"type":46,"value":590}," Engineering team (relevant product area)\n",{"type":41,"tag":163,"props":592,"children":593},{},[594],{"type":46,"value":560},{"type":46,"value":596}," Confirmed bug, infrastructure issue, needs code change, requires system-level investigation\n",{"type":41,"tag":163,"props":598,"children":599},{},[600],{"type":46,"value":567},{"type":46,"value":602}," Full reproduction steps, environment details, logs or error messages, business impact, customer timeline",{"type":41,"tag":145,"props":604,"children":606},{"id":605},"l2-product",[607],{"type":46,"value":608},"L2 → Product",{"type":41,"tag":53,"props":610,"children":611},{},[612,616,617,621,623,627,629,633],{"type":41,"tag":163,"props":613,"children":614},{},[615],{"type":46,"value":546},{"type":46,"value":584},{"type":41,"tag":163,"props":618,"children":619},{},[620],{"type":46,"value":553},{"type":46,"value":622}," Product management\n",{"type":41,"tag":163,"props":624,"children":625},{},[626],{"type":46,"value":560},{"type":46,"value":628}," Feature gap causing customer pain, design decision needed, workflow doesn't match customer expectations, competing customer needs require prioritization\n",{"type":41,"tag":163,"props":630,"children":631},{},[632],{"type":46,"value":567},{"type":46,"value":634}," Customer use case, business impact, frequency of request, competitive pressure (if known)",{"type":41,"tag":145,"props":636,"children":638},{"id":637},"any-security",[639],{"type":46,"value":640},"Any → Security",{"type":41,"tag":53,"props":642,"children":643},{},[644,648,650,654,656,660,662,666,668,673],{"type":41,"tag":163,"props":645,"children":646},{},[647],{"type":46,"value":546},{"type":46,"value":649}," Any support tier\n",{"type":41,"tag":163,"props":651,"children":652},{},[653],{"type":46,"value":553},{"type":46,"value":655}," Security team\n",{"type":41,"tag":163,"props":657,"children":658},{},[659],{"type":46,"value":560},{"type":46,"value":661}," Potential data exposure, unauthorized access, vulnerability report, compliance concern\n",{"type":41,"tag":163,"props":663,"children":664},{},[665],{"type":46,"value":567},{"type":46,"value":667}," What was observed, who\u002Fwhat is potentially affected, immediate containment steps taken, urgency assessment\n",{"type":41,"tag":163,"props":669,"children":670},{},[671],{"type":46,"value":672},"Note:",{"type":46,"value":674}," Security escalations bypass normal tier progression — escalate immediately regardless of your level",{"type":41,"tag":145,"props":676,"children":678},{"id":677},"any-leadership",[679],{"type":46,"value":680},"Any → Leadership",{"type":41,"tag":53,"props":682,"children":683},{},[684,688,690,694,696,700,702,706],{"type":41,"tag":163,"props":685,"children":686},{},[687],{"type":46,"value":546},{"type":46,"value":689}," Any tier (usually L2 or manager)\n",{"type":41,"tag":163,"props":691,"children":692},{},[693],{"type":46,"value":553},{"type":46,"value":695}," Support leadership, executive team\n",{"type":41,"tag":163,"props":697,"children":698},{},[699],{"type":46,"value":560},{"type":46,"value":701}," High-revenue customer threatening churn, SLA breach on critical account, cross-functional decision needed, exception to policy required, PR or legal risk\n",{"type":41,"tag":163,"props":703,"children":704},{},[705],{"type":46,"value":567},{"type":46,"value":707}," Full business context, revenue at risk, what's been tried, specific decision or action needed, deadline",{"type":41,"tag":73,"props":709,"children":711},{"id":710},"business-impact-assessment",[712],{"type":46,"value":713},"Business Impact Assessment",{"type":41,"tag":53,"props":715,"children":716},{},[717],{"type":46,"value":718},"When escalating, quantify impact where possible:",{"type":41,"tag":145,"props":720,"children":722},{"id":721},"impact-dimensions",[723],{"type":46,"value":724},"Impact Dimensions",{"type":41,"tag":726,"props":727,"children":728},"table",{},[729,748],{"type":41,"tag":730,"props":731,"children":732},"thead",{},[733],{"type":41,"tag":734,"props":735,"children":736},"tr",{},[737,743],{"type":41,"tag":738,"props":739,"children":740},"th",{},[741],{"type":46,"value":742},"Dimension",{"type":41,"tag":738,"props":744,"children":745},{},[746],{"type":46,"value":747},"Questions to Answer",{"type":41,"tag":749,"props":750,"children":751},"tbody",{},[752,768,783,798,813,829],{"type":41,"tag":734,"props":753,"children":754},{},[755,763],{"type":41,"tag":756,"props":757,"children":758},"td",{},[759],{"type":41,"tag":163,"props":760,"children":761},{},[762],{"type":46,"value":300},{"type":41,"tag":756,"props":764,"children":765},{},[766],{"type":46,"value":767},"How many customers\u002Fusers are affected? Is it growing?",{"type":41,"tag":734,"props":769,"children":770},{},[771,778],{"type":41,"tag":756,"props":772,"children":773},{},[774],{"type":41,"tag":163,"props":775,"children":776},{},[777],{"type":46,"value":310},{"type":41,"tag":756,"props":779,"children":780},{},[781],{"type":46,"value":782},"How severely are they impacted? Blocked vs. inconvenienced?",{"type":41,"tag":734,"props":784,"children":785},{},[786,793],{"type":41,"tag":756,"props":787,"children":788},{},[789],{"type":41,"tag":163,"props":790,"children":791},{},[792],{"type":46,"value":320},{"type":41,"tag":756,"props":794,"children":795},{},[796],{"type":46,"value":797},"How long has this been going on? How long until it's critical?",{"type":41,"tag":734,"props":799,"children":800},{},[801,808],{"type":41,"tag":756,"props":802,"children":803},{},[804],{"type":41,"tag":163,"props":805,"children":806},{},[807],{"type":46,"value":330},{"type":41,"tag":756,"props":809,"children":810},{},[811],{"type":46,"value":812},"What's the ARR at risk? Are there pending deals affected?",{"type":41,"tag":734,"props":814,"children":815},{},[816,824],{"type":41,"tag":756,"props":817,"children":818},{},[819],{"type":41,"tag":163,"props":820,"children":821},{},[822],{"type":46,"value":823},"Reputation",{"type":41,"tag":756,"props":825,"children":826},{},[827],{"type":46,"value":828},"Could this become public? Is it a reference customer?",{"type":41,"tag":734,"props":830,"children":831},{},[832,840],{"type":41,"tag":756,"props":833,"children":834},{},[835],{"type":41,"tag":163,"props":836,"children":837},{},[838],{"type":46,"value":839},"Contractual",{"type":41,"tag":756,"props":841,"children":842},{},[843],{"type":46,"value":844},"Are SLAs being breached? Are there contractual obligations?",{"type":41,"tag":145,"props":846,"children":848},{"id":847},"severity-shorthand",[849],{"type":46,"value":850},"Severity Shorthand",{"type":41,"tag":98,"props":852,"children":853},{},[854,864,874],{"type":41,"tag":102,"props":855,"children":856},{},[857,862],{"type":41,"tag":163,"props":858,"children":859},{},[860],{"type":46,"value":861},"Critical",{"type":46,"value":863},": Production down, data at risk, security breach, or multiple high-value customers affected. Needs immediate attention.",{"type":41,"tag":102,"props":865,"children":866},{},[867,872],{"type":41,"tag":163,"props":868,"children":869},{},[870],{"type":46,"value":871},"High",{"type":46,"value":873},": Major functionality broken, key customer blocked, SLA at risk. Needs same-day attention.",{"type":41,"tag":102,"props":875,"children":876},{},[877,882],{"type":41,"tag":163,"props":878,"children":879},{},[880],{"type":46,"value":881},"Medium",{"type":46,"value":883},": Significant issue with workaround, important but not urgent business impact. Needs attention this week.",{"type":41,"tag":73,"props":885,"children":887},{"id":886},"writing-reproduction-steps",[888],{"type":46,"value":889},"Writing Reproduction Steps",{"type":41,"tag":53,"props":891,"children":892},{},[893],{"type":46,"value":894},"Good reproduction steps are the single most valuable thing in a bug escalation. Follow these practices:",{"type":41,"tag":896,"props":897,"children":898},"ol",{},[899,909,919,929,939,949,959],{"type":41,"tag":102,"props":900,"children":901},{},[902,907],{"type":41,"tag":163,"props":903,"children":904},{},[905],{"type":46,"value":906},"Start from a clean state",{"type":46,"value":908},": Describe the starting point (account type, configuration, permissions)",{"type":41,"tag":102,"props":910,"children":911},{},[912,917],{"type":41,"tag":163,"props":913,"children":914},{},[915],{"type":46,"value":916},"Be specific",{"type":46,"value":918},": \"Click the Export button in the top-right of the Dashboard page\" not \"try to export\"",{"type":41,"tag":102,"props":920,"children":921},{},[922,927],{"type":41,"tag":163,"props":923,"children":924},{},[925],{"type":46,"value":926},"Include exact values",{"type":46,"value":928},": Use specific inputs, dates, IDs — not \"enter some data\"",{"type":41,"tag":102,"props":930,"children":931},{},[932,937],{"type":41,"tag":163,"props":933,"children":934},{},[935],{"type":46,"value":936},"Note the environment",{"type":46,"value":938},": Browser, OS, account type, feature flags, plan level",{"type":41,"tag":102,"props":940,"children":941},{},[942,947],{"type":41,"tag":163,"props":943,"children":944},{},[945],{"type":46,"value":946},"Capture the frequency",{"type":46,"value":948},": Always reproducible? Intermittent? Only under certain conditions?",{"type":41,"tag":102,"props":950,"children":951},{},[952,957],{"type":41,"tag":163,"props":953,"children":954},{},[955],{"type":46,"value":956},"Include evidence",{"type":46,"value":958},": Screenshots, error messages (exact text), network logs, console output",{"type":41,"tag":102,"props":960,"children":961},{},[962,967],{"type":41,"tag":163,"props":963,"children":964},{},[965],{"type":46,"value":966},"Note what you've ruled out",{"type":46,"value":968},": \"Tested in Chrome and Firefox — same behavior\" \"Not account-specific — reproduced on test account\"",{"type":41,"tag":73,"props":970,"children":972},{"id":971},"follow-up-cadence-after-escalation",[973],{"type":46,"value":974},"Follow-up Cadence After Escalation",{"type":41,"tag":53,"props":976,"children":977},{},[978],{"type":46,"value":979},"Don't escalate and forget. Maintain ownership of the customer relationship.",{"type":41,"tag":726,"props":981,"children":982},{},[983,1004],{"type":41,"tag":730,"props":984,"children":985},{},[986],{"type":41,"tag":734,"props":987,"children":988},{},[989,994,999],{"type":41,"tag":738,"props":990,"children":991},{},[992],{"type":46,"value":993},"Severity",{"type":41,"tag":738,"props":995,"children":996},{},[997],{"type":46,"value":998},"Internal Follow-up",{"type":41,"tag":738,"props":1000,"children":1001},{},[1002],{"type":46,"value":1003},"Customer Update",{"type":41,"tag":749,"props":1005,"children":1006},{},[1007,1027,1047],{"type":41,"tag":734,"props":1008,"children":1009},{},[1010,1017,1022],{"type":41,"tag":756,"props":1011,"children":1012},{},[1013],{"type":41,"tag":163,"props":1014,"children":1015},{},[1016],{"type":46,"value":861},{"type":41,"tag":756,"props":1018,"children":1019},{},[1020],{"type":46,"value":1021},"Every 2 hours",{"type":41,"tag":756,"props":1023,"children":1024},{},[1025],{"type":46,"value":1026},"Every 2-4 hours (or per SLA)",{"type":41,"tag":734,"props":1028,"children":1029},{},[1030,1037,1042],{"type":41,"tag":756,"props":1031,"children":1032},{},[1033],{"type":41,"tag":163,"props":1034,"children":1035},{},[1036],{"type":46,"value":871},{"type":41,"tag":756,"props":1038,"children":1039},{},[1040],{"type":46,"value":1041},"Every 4 hours",{"type":41,"tag":756,"props":1043,"children":1044},{},[1045],{"type":46,"value":1046},"Every 4-8 hours",{"type":41,"tag":734,"props":1048,"children":1049},{},[1050,1057,1062],{"type":41,"tag":756,"props":1051,"children":1052},{},[1053],{"type":41,"tag":163,"props":1054,"children":1055},{},[1056],{"type":46,"value":881},{"type":41,"tag":756,"props":1058,"children":1059},{},[1060],{"type":46,"value":1061},"Daily",{"type":41,"tag":756,"props":1063,"children":1064},{},[1065],{"type":46,"value":1066},"Every 1-2 business days",{"type":41,"tag":145,"props":1068,"children":1070},{"id":1069},"follow-up-actions",[1071],{"type":46,"value":1072},"Follow-up Actions",{"type":41,"tag":98,"props":1074,"children":1075},{},[1076,1081,1086,1091,1096],{"type":41,"tag":102,"props":1077,"children":1078},{},[1079],{"type":46,"value":1080},"Check with the receiving team for progress",{"type":41,"tag":102,"props":1082,"children":1083},{},[1084],{"type":46,"value":1085},"Update the customer even if there's no new information (\"We're still investigating — here's what we know so far\")",{"type":41,"tag":102,"props":1087,"children":1088},{},[1089],{"type":46,"value":1090},"Adjust severity if the situation changes (better or worse)",{"type":41,"tag":102,"props":1092,"children":1093},{},[1094],{"type":46,"value":1095},"Document all updates in the ticket for audit trail",{"type":41,"tag":102,"props":1097,"children":1098},{},[1099],{"type":46,"value":1100},"Close the loop when resolved: confirm with customer, update internal tracking, capture learnings",{"type":41,"tag":73,"props":1102,"children":1104},{"id":1103},"de-escalation",[1105],{"type":46,"value":1106},"De-escalation",{"type":41,"tag":53,"props":1108,"children":1109},{},[1110],{"type":46,"value":1111},"Not every escalation stays escalated. De-escalate when:",{"type":41,"tag":98,"props":1113,"children":1114},{},[1115,1120,1125,1130],{"type":41,"tag":102,"props":1116,"children":1117},{},[1118],{"type":46,"value":1119},"Root cause is found and it's a support-resolvable issue",{"type":41,"tag":102,"props":1121,"children":1122},{},[1123],{"type":46,"value":1124},"A workaround is found that unblocks the customer",{"type":41,"tag":102,"props":1126,"children":1127},{},[1128],{"type":46,"value":1129},"The issue resolves itself (but still document root cause)",{"type":41,"tag":102,"props":1131,"children":1132},{},[1133],{"type":46,"value":1134},"New information changes the severity assessment",{"type":41,"tag":53,"props":1136,"children":1137},{},[1138],{"type":46,"value":1139},"When de-escalating:",{"type":41,"tag":98,"props":1141,"children":1142},{},[1143,1148,1153,1158],{"type":41,"tag":102,"props":1144,"children":1145},{},[1146],{"type":46,"value":1147},"Notify the team you escalated to",{"type":41,"tag":102,"props":1149,"children":1150},{},[1151],{"type":46,"value":1152},"Update the ticket with the resolution",{"type":41,"tag":102,"props":1154,"children":1155},{},[1156],{"type":46,"value":1157},"Inform the customer of the resolution",{"type":41,"tag":102,"props":1159,"children":1160},{},[1161],{"type":46,"value":1162},"Document what was learned for future reference",{"type":41,"tag":73,"props":1164,"children":1166},{"id":1165},"escalation-best-practices",[1167],{"type":46,"value":1168},"Escalation Best Practices",{"type":41,"tag":896,"props":1170,"children":1171},{},[1172,1177,1182,1187,1192,1197,1202],{"type":41,"tag":102,"props":1173,"children":1174},{},[1175],{"type":46,"value":1176},"Always quantify impact — vague escalations get deprioritized",{"type":41,"tag":102,"props":1178,"children":1179},{},[1180],{"type":46,"value":1181},"Include reproduction steps for bugs — this is the #1 thing engineering needs",{"type":41,"tag":102,"props":1183,"children":1184},{},[1185],{"type":46,"value":1186},"Be clear about what you need — \"investigate\" vs. \"fix\" vs. \"decide\" are different asks",{"type":41,"tag":102,"props":1188,"children":1189},{},[1190],{"type":46,"value":1191},"Set and communicate a deadline — urgency without a deadline is ambiguous",{"type":41,"tag":102,"props":1193,"children":1194},{},[1195],{"type":46,"value":1196},"Maintain ownership of the customer relationship even after escalating the technical issue",{"type":41,"tag":102,"props":1198,"children":1199},{},[1200],{"type":46,"value":1201},"Follow up proactively — don't wait for the receiving team to come to you",{"type":41,"tag":102,"props":1203,"children":1204},{},[1205],{"type":46,"value":1206},"Document everything — the escalation trail is valuable for pattern detection and process improvement",{"items":1208,"total":1323},[1209,1225,1241,1257,1275,1294,1310],{"slug":1210,"name":1210,"fn":1211,"description":1212,"org":1213,"tags":1214,"stars":23,"repoUrl":24,"updatedAt":1224},"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},[1215,1218,1221],{"name":1216,"slug":1217,"type":16},"Accessibility","accessibility",{"name":1219,"slug":1220,"type":16},"Design","design",{"name":1222,"slug":1223,"type":16},"WCAG","wcag","2026-04-06T17:58:05.682394",{"slug":1226,"name":1226,"fn":1227,"description":1228,"org":1229,"tags":1230,"stars":23,"repoUrl":24,"updatedAt":1240},"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},[1231,1234,1237],{"name":1232,"slug":1233,"type":16},"CRM","crm",{"name":1235,"slug":1236,"type":16},"Research","research",{"name":1238,"slug":1239,"type":16},"Sales","sales","2026-04-06T17:56:41.410418",{"slug":1242,"name":1242,"fn":1243,"description":1244,"org":1245,"tags":1246,"stars":23,"repoUrl":24,"updatedAt":1256},"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},[1247,1250,1253],{"name":1248,"slug":1249,"type":16},"Analytics","analytics",{"name":1251,"slug":1252,"type":16},"Data Analysis","data-analysis",{"name":1254,"slug":1255,"type":16},"SQL","sql","2026-04-06T17:57:21.593647",{"slug":1258,"name":1258,"fn":1259,"description":1260,"org":1261,"tags":1262,"stars":23,"repoUrl":24,"updatedAt":1274},"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},[1263,1266,1268,1271],{"name":1264,"slug":1265,"type":16},"ADR","adr",{"name":1267,"slug":1258,"type":16},"Architecture",{"name":1269,"slug":1270,"type":16},"Documentation","documentation",{"name":1272,"slug":1273,"type":16},"Engineering","engineering","2026-04-06T17:57:49.26444",{"slug":1276,"name":1276,"fn":1277,"description":1278,"org":1279,"tags":1280,"stars":23,"repoUrl":24,"updatedAt":1293},"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},[1281,1284,1287,1290],{"name":1282,"slug":1283,"type":16},"Audit","audit",{"name":1285,"slug":1286,"type":16},"Finance","finance",{"name":1288,"slug":1289,"type":16},"Regulatory Compliance","regulatory-compliance",{"name":1291,"slug":1292,"type":16},"SOX","sox","2026-04-06T17:57:36.714815",{"slug":1295,"name":1295,"fn":1296,"description":1297,"org":1298,"tags":1299,"stars":23,"repoUrl":24,"updatedAt":1309},"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},[1300,1303,1306],{"name":1301,"slug":1302,"type":16},"Branding","branding",{"name":1304,"slug":1305,"type":16},"Marketing","marketing",{"name":1307,"slug":1308,"type":16},"Writing","writing","2026-04-06T17:58:19.548331",{"slug":1311,"name":1311,"fn":1312,"description":1313,"org":1314,"tags":1315,"stars":23,"repoUrl":24,"updatedAt":1322},"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},[1316,1317,1318,1321],{"name":1301,"slug":1302,"type":16},{"name":21,"slug":22,"type":16},{"name":1319,"slug":1320,"type":16},"Content Creation","content-creation",{"name":1307,"slug":1308,"type":16},"2026-04-06T18:00:23.528956",200,{"items":1325,"total":1502},[1326,1345,1357,1369,1388,1399,1420,1440,1450,1465,1473,1486],{"slug":1327,"name":1327,"fn":1328,"description":1329,"org":1330,"tags":1331,"stars":1342,"repoUrl":1343,"updatedAt":1344},"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},[1332,1335,1336,1339],{"name":1333,"slug":1334,"type":16},"Creative","creative",{"name":1219,"slug":1220,"type":16},{"name":1337,"slug":1338,"type":16},"Generative Art","generative-art",{"name":1340,"slug":1341,"type":16},"JavaScript","javascript",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-04-06T17:56:15.455818",{"slug":1346,"name":1346,"fn":1347,"description":1348,"org":1349,"tags":1350,"stars":1342,"repoUrl":1343,"updatedAt":1356},"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},[1351,1352,1353],{"name":1301,"slug":1302,"type":16},{"name":1219,"slug":1220,"type":16},{"name":1354,"slug":1355,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":1358,"name":1358,"fn":1359,"description":1360,"org":1361,"tags":1362,"stars":1342,"repoUrl":1343,"updatedAt":1368},"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},[1363,1364,1365],{"name":1333,"slug":1334,"type":16},{"name":1219,"slug":1220,"type":16},{"name":1366,"slug":1367,"type":16},"PDF","pdf","2026-04-06T17:56:03.794732",{"slug":1370,"name":1370,"fn":1371,"description":1372,"org":1373,"tags":1374,"stars":1342,"repoUrl":1343,"updatedAt":1387},"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},[1375,1378,1379,1382,1384],{"name":1376,"slug":1377,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":1380,"slug":1381,"type":16},"Anthropic SDK","anthropic-sdk",{"name":1383,"slug":1370,"type":16},"Claude API",{"name":1385,"slug":1386,"type":16},"LLM","llm","2026-07-28T05:36:08.213335",{"slug":1389,"name":1389,"fn":1390,"description":1391,"org":1392,"tags":1393,"stars":1342,"repoUrl":1343,"updatedAt":1398},"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},[1394,1395],{"name":1269,"slug":1270,"type":16},{"name":1396,"slug":1397,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":1400,"name":1400,"fn":1401,"description":1402,"org":1403,"tags":1404,"stars":1342,"repoUrl":1343,"updatedAt":1419},"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},[1405,1408,1410,1413,1416],{"name":1406,"slug":1407,"type":16},"Documents","documents",{"name":1409,"slug":1400,"type":16},"DOCX",{"name":1411,"slug":1412,"type":16},"Office","office",{"name":1414,"slug":1415,"type":16},"Templates","templates",{"name":1417,"slug":1418,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":1421,"name":1421,"fn":1422,"description":1423,"org":1424,"tags":1425,"stars":1342,"repoUrl":1343,"updatedAt":1439},"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},[1426,1427,1430,1433,1436],{"name":1219,"slug":1220,"type":16},{"name":1428,"slug":1429,"type":16},"Frontend","frontend",{"name":1431,"slug":1432,"type":16},"React","react",{"name":1434,"slug":1435,"type":16},"Tailwind CSS","tailwind-css",{"name":1437,"slug":1438,"type":16},"UI Components","ui-components","2026-04-06T17:56:16.723469",{"slug":1441,"name":1441,"fn":1442,"description":1443,"org":1444,"tags":1445,"stars":1342,"repoUrl":1343,"updatedAt":1449},"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},[1446,1447,1448],{"name":21,"slug":22,"type":16},{"name":1414,"slug":1415,"type":16},{"name":1307,"slug":1308,"type":16},"2026-04-06T17:56:20.695522",{"slug":1451,"name":1451,"fn":1452,"description":1453,"org":1454,"tags":1455,"stars":1342,"repoUrl":1343,"updatedAt":1464},"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},[1456,1457,1460,1461],{"name":1376,"slug":1377,"type":16},{"name":1458,"slug":1459,"type":16},"API Development","api-development",{"name":1385,"slug":1386,"type":16},{"name":1462,"slug":1463,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":1367,"name":1367,"fn":1466,"description":1467,"org":1468,"tags":1469,"stars":1342,"repoUrl":1343,"updatedAt":1472},"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},[1470,1471],{"name":1406,"slug":1407,"type":16},{"name":1366,"slug":1367,"type":16},"2026-04-06T17:56:02.483316",{"slug":1474,"name":1474,"fn":1475,"description":1476,"org":1477,"tags":1478,"stars":1342,"repoUrl":1343,"updatedAt":1485},"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},[1479,1482],{"name":1480,"slug":1481,"type":16},"PowerPoint","powerpoint",{"name":1483,"slug":1484,"type":16},"Presentations","presentations","2026-07-18T05:16:24.1471",{"slug":1487,"name":1487,"fn":1488,"description":1489,"org":1490,"tags":1491,"stars":1342,"repoUrl":1343,"updatedAt":1501},"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},[1492,1493,1494,1497,1500],{"name":1376,"slug":1377,"type":16},{"name":1269,"slug":1270,"type":16},{"name":1495,"slug":1496,"type":16},"Evals","evals",{"name":1498,"slug":1499,"type":16},"Performance","performance",{"name":1396,"slug":1397,"type":16},"2026-04-19T06:45:40.804",490]