[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD1W2XTGJCCZPWFYM9EFCE":3,"skill-same:01M6AD1W2XTGJCCZPWFYM9EFCE":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6AD1W2XTGJCCZPWFYM9EFCE","support-ticket-triage",null,"Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it's a duplicate or known issue before routing.","Significant-Gravitas\u002Fskills-catalog","Significant-Gravitas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130738209?v=4","01M6AC83EPDGBFN19MWYRREJD0","AutoGPT","01M6ACEY98TKHDWJH0B93PHNMG",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fsupport-ticket-triage\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fsupport-ticket-triage\u002FSKILL.md",[],[20,21,22,23,24,25,26,27],"triage","support","support ticket triage","github","customer","routing","https","plugins","2026-11-10 10:12:30",false,"---\nname: support-ticket-triage\ndescription: Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it's a duplicate or known issue before routing.\nargument-hint: \u003Cticket or issue description>\nlicense: Apache-2.0\nmetadata:\n  author: Anthropic\n  source: anthropics\u002Fknowledge-work-plugins\u002Fcustomer-support\u002Fskills\u002Fticket-triage\n  source_url: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002F1c7187c4fc17feefa6cde39517f12dae1249e6c4\u002Fcustomer-support\u002Fskills\u002Fticket-triage\u002FSKILL.md\n  upstream-commit: 1c7187c4fc17feefa6cde39517f12dae1249e6c4\n  original-name: ticket-triage\n  packaged-by: AutoGPT\n  packaged-on: '2026-09-25'\n---\n\n> Packaging adaptation by AutoGPT, 2026-09-25. Original authorship and licence are retained. Changes are limited to the recorded name, metadata and local references; see ATTRIBUTION.md in this package.\n\n\n# \u002Fticket-triage\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](references\u002FCONNECTORS.md).\n\nCategorize, prioritize, and route an incoming support ticket or customer issue. Produces a structured triage assessment with a suggested initial response.\n\n## Usage\n\n```\n\u002Fticket-triage \u003Cticket text, customer message, or issue description>\n```\n\nExamples:\n- `\u002Fticket-triage Customer says their dashboard has been showing a blank page since this morning`\n- `\u002Fticket-triage \"I was charged twice for my subscription this month\"`\n- `\u002Fticket-triage User can't connect their SSO — getting a 403 error on the callback URL`\n- `\u002Fticket-triage Feature request: they want to export reports as PDF`\n\n## Workflow\n\n### 1. Parse the Issue\n\nRead the input and extract:\n\n- **Core problem**: What is the customer actually experiencing?\n- **Symptoms**: What specific behavior or error are they seeing?\n- **Customer context**: Who is this? Any account details, plan level, or history available?\n- **Urgency signals**: Are they blocked? Is this production? How many users affected?\n- **Emotional state**: Frustrated, confused, matter-of-fact, escalating?\n\n### 2. Categorize and Prioritize\n\nUsing the category taxonomy and priority framework below:\n\n- Assign a **primary category** (bug, how-to, feature request, billing, account, integration, security, data, performance) and an optional secondary category\n- Assign a **priority** (P1–P4) based on impact and urgency\n- Identify the **product area** the issue maps to\n\n### 3. Check for Duplicates and Known Issues\n\nBefore routing, check available sources:\n\n- **~~support platform**: Search for similar open or recently resolved tickets\n- **~~knowledge base**: Check for known issues or existing documentation\n- **~~project tracker**: Check if there's an existing bug report or feature request\n\nApply the duplicate detection process below.\n\n### 4. Determine Routing\n\nUsing the routing rules below, recommend which team or queue should handle this based on category and complexity.\n\n### 5. Generate Triage Output\n\n```\n## Triage: [One-line issue summary]\n\n**Category:** [Primary] \u002F [Secondary if applicable]\n**Priority:** [P1-P4] — [Brief justification]\n**Product area:** [Area\u002Fteam]\n\n### Issue Summary\n[2-3 sentence summary of what the customer is experiencing]\n\n### Key Details\n- **Customer:** [Name\u002Faccount if known]\n- **Impact:** [Who and what is affected]\n- **Workaround:** [Available \u002F Not available \u002F Unknown]\n- **Related tickets:** [Links to similar issues if found]\n- **Known issue:** [Yes — link \u002F No \u002F Checking]\n\n### Routing Recommendation\n**Route to:** [Team or queue]\n**Why:** [Brief reasoning]\n\n### Suggested Initial Response\n[Draft first response to the customer — acknowledge the issue,\nset expectations, provide workaround if available.\nUse the auto-response templates below as a starting point.]\n\n### Internal Notes\n- [Any additional context for the agent picking this up]\n- [Reproduction hints if it's a bug]\n- [Escalation triggers to watch for]\n```\n\n### 6. Offer Next Steps\n\nAfter presenting the triage:\n- \"Want me to draft a full response to the customer?\"\n- \"Should I search for more context on this issue?\"\n- \"Want me to check if this is a known bug in the tracker?\"\n- \"Should I escalate this? I can package it with \u002Fcustomer-escalation.\"\n\n---\n\n## Category Taxonomy\n\nAssign every ticket a **primary category** and optionally a **secondary category**:\n\n| Category | Description | Signal Words |\n|----------|-------------|-------------|\n| **Bug** | Product is behaving incorrectly or unexpectedly | Error, broken, crash, not working, unexpected, wrong, failing |\n| **How-to** | Customer needs guidance on using the product | How do I, can I, where is, setting up, configure, help with |\n| **Feature request** | Customer wants a capability that doesn't exist | Would be great if, wish I could, any plans to, requesting |\n| **Billing** | Payment, subscription, invoice, or pricing issues | Charge, invoice, payment, subscription, refund, upgrade, downgrade |\n| **Account** | Account access, permissions, settings, or user management | Login, password, access, permission, SSO, locked out, can't sign in |\n| **Integration** | Issues connecting to third-party tools or APIs | API, webhook, integration, connect, OAuth, sync, third-party |\n| **Security** | Security concerns, data access, or compliance questions | Data breach, unauthorized, compliance, GDPR, SOC 2, vulnerability |\n| **Data** | Data quality, migration, import\u002Fexport issues | Missing data, export, import, migration, incorrect data, duplicates |\n| **Performance** | Speed, reliability, or availability issues | Slow, timeout, latency, down, unavailable, degraded |\n\n### Category Determination Tips\n\n- If the customer reports **both** a bug and a feature request, the bug is primary\n- If they can't log in due to a bug, category is **Bug** (not Account) — root cause drives the category\n- \"It used to work and now it doesn't\" = **Bug**\n- \"I want it to work differently\" = **Feature request**\n- \"How do I make it work?\" = **How-to**\n- When in doubt, lean toward **Bug** — it's better to investigate than dismiss\n\n## Priority Framework\n\n### P1 — Critical\n**Criteria:** Production system down, data loss or corruption, security breach, all or most users affected.\n\n- The customer cannot use the product at all\n- Data is being lost, corrupted, or exposed\n- A security incident is in progress\n- The issue is worsening or expanding in scope\n\n**SLA expectation:** Respond within 1 hour. Continuous work until resolved or mitigated. Updates every 1-2 hours.\n\n### P2 — High\n**Criteria:** Major feature broken, significant workflow blocked, many users affected, no workaround.\n\n- A core workflow is broken but the product is partially usable\n- Multiple users are affected or a key account is impacted\n- The issue is blocking time-sensitive work\n- No reasonable workaround exists\n\n**SLA expectation:** Respond within 4 hours. Active investigation same day. Updates every 4 hours.\n\n### P3 — Medium\n**Criteria:** Feature partially broken, workaround available, single user or small team affected.\n\n- A feature isn't working correctly but a workaround exists\n- The issue is inconvenient but not blocking critical work\n- A single user or small team is affected\n- The customer is not escalating urgently\n\n**SLA expectation:** Respond within 1 business day. Resolution or update within 3 business days.\n\n### P4 — Low\n**Criteria:** Minor inconvenience, cosmetic issue, general question, feature request.\n\n- Cosmetic or UI issues that don't affect functionality\n- Feature requests and enhancement ideas\n- General questions or how-to inquiries\n- Issues with simple, documented solutions\n\n**SLA expectation:** Respond within 2 business days. Resolution at normal pace.\n\n### Priority Escalation Triggers\n\nAutomatically bump priority up when:\n- Customer has been waiting longer than the SLA allows\n- Multiple customers report the same issue (pattern detected)\n- The customer explicitly escalates or mentions executive involvement\n- A workaround that was in place stops working\n- The issue expands in scope (more users, more data, new symptoms)\n\n## Routing Rules\n\nRoute tickets based on category and complexity:\n\n| Route to | When |\n|----------|------|\n| **Tier 1 (frontline support)** | How-to questions, known issues with documented solutions, billing inquiries, password resets |\n| **Tier 2 (senior support)** | Bugs requiring investigation, complex configuration, integration troubleshooting, account issues |\n| **Engineering** | Confirmed bugs needing code fixes, infrastructure issues, performance degradation |\n| **Product** | Feature requests with significant demand, design decisions, workflow gaps |\n| **Security** | Data access concerns, vulnerability reports, compliance questions |\n| **Billing\u002FFinance** | Refund requests, contract disputes, complex billing adjustments |\n\n## Duplicate Detection\n\nBefore creating a new ticket or routing, check for duplicates:\n\n1. **Search by symptom**: Look for tickets with similar error messages or descriptions\n2. **Search by customer**: Check if this customer has an open ticket for the same issue\n3. **Search by product area**: Look for recent tickets in the same feature area\n4. **Check known issues**: Compare against documented known issues\n\n**If a duplicate is found:**\n- Link the new ticket to the existing one\n- Notify the customer that this is a known issue being tracked\n- Add any new information from the new report to the existing ticket\n- Bump priority if the new report adds urgency (more customers affected, etc.)\n\n## Auto-Response Templates by Category\n\n### Bug — Initial Response\n```\nThank you for reporting this. I can see how [specific impact]\nwould be disruptive for your work.\n\nI've logged this as a [priority] issue and our team is\ninvestigating. [If workaround exists: \"In the meantime, you\ncan [workaround].\"]\n\nI'll update you within [SLA timeframe] with what we find.\n```\n\n### How-to — Initial Response\n```\nGreat question! [Direct answer or link to documentation]\n\n[If more complex: \"Let me walk you through the steps:\"]\n[Steps or guidance]\n\nLet me know if that helps, or if you have any follow-up\nquestions.\n```\n\n### Feature Request — Initial Response\n```\nThank you for this suggestion — I can see why [capability]\nwould be valuable for your workflow.\n\nI've documented this and shared it with our product team.\nWhile I can't commit to a specific timeline, your feedback\ndirectly informs our roadmap priorities.\n\n[If alternative exists: \"In the meantime, you might find\n[alternative] helpful for achieving something similar.\"]\n```\n\n### Billing — Initial Response\n```\nI understand billing issues need prompt attention. Let me\nlook into this for you.\n\n[If straightforward: resolution details]\n[If complex: \"I'm reviewing your account now and will have\nan answer for you within [timeframe].\"]\n```\n\n### Security — Initial Response\n```\nThank you for flagging this — we take security concerns\nseriously and are reviewing this immediately.\n\nI've escalated this to our security team for investigation.\nWe'll follow up with you within [timeframe] with our findings.\n\n[If action is needed: \"In the meantime, we recommend\n[protective action].\"]\n```\n\n## Triage Best Practices\n\n1. Read the full ticket before categorizing — context in later messages often changes the assessment\n2. Categorize by **root cause**, not just the symptom described\n3. When in doubt on priority, err on the side of higher — it's easier to de-escalate than to recover from a missed SLA\n4. Always check for duplicates and known issues before routing\n5. Write internal notes that help the next person pick up context quickly\n6. Include what you've already checked or ruled out to avoid duplicate investigation\n7. Flag patterns — if you're seeing the same issue repeatedly, escalate the pattern even if individual tickets are low priority\n","> Packaging adaptation by AutoGPT, 2026-09-25. Original authorship and licence are retained. Changes are limited to the recorded name, metadata and local references; see ATTRIBUTION.md in this package.\n\n\n# \u002Fticket-triage\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](references\u002FCONNECTORS.md).\n\nCategorize, prioritize, and route an incoming support ticket or customer issue. Produces a structured triage assessment with a suggested initial response.\n\n## Usage\n\n```\n\u002Fticket-triage \u003Cticket text, customer message, or issue description>\n```\n\nExamples:\n- `\u002Fticket-triage Customer says their dashboard has been showing a blank page since this morning`\n- `\u002Fticket-triage \"I was charged twice for my subscription this month\"`\n- `\u002Fticket-triage User can't connect their SSO — getting a 403 error on the callback URL`\n- `\u002Fticket-triage Feature request: they want to export reports as PDF`\n\n## Workflow\n\n### 1. Parse the Issue\n\nRead the input and extract:\n\n- **Core problem**: What is the customer actually experiencing?\n- **Symptoms**: What specific behavior or error are they seeing?\n- **Customer context**: Who is this? Any account details, plan level, or history available?\n- **Urgency signals**: Are they blocked? Is this production? How many users affected?\n- **Emotional state**: Frustrated, confused, matter-of-fact, escalating?\n\n### 2. Categorize and Prioritize\n\nUsing the category taxonomy and priority framework below:\n\n- Assign a **primary category** (bug, how-to, feature request, billing, account, integration, security, data, performance) and an optional secondary category\n- Assign a **priority** (P1–P4) based on impact and urgency\n- Identify the **product area** the issue maps to\n\n### 3. Check for Duplicates and Known Issues\n\nBefore routing, check available sources:\n\n- **~~support platform**: Search for similar open or recently resolved tickets\n- **~~knowledge base**: Check for known issues or existing documentation\n- **~~project tracker**: Check if there's an existing bug report or feature request\n\nApply the duplicate detection process below.\n\n### 4. Determine Routing\n\nUsing the routing rules below, recommend which team or queue should handle this based on category and complexity.\n\n### 5. Generate Triage Output\n\n```\n## Triage: [One-line issue summary]\n\n**Category:** [Primary] \u002F [Secondary if applicable]\n**Priority:** [P1-P4] — [Brief justification]\n**Product area:** [Area\u002Fteam]\n\n### Issue Summary\n[2-3 sentence summary of what the customer is experiencing]\n\n### Key Details\n- **Customer:** [Name\u002Faccount if known]\n- **Impact:** [Who and what is affected]\n- **Workaround:** [Available \u002F Not available \u002F Unknown]\n- **Related tickets:** [Links to similar issues if found]\n- **Known issue:** [Yes — link \u002F No \u002F Checking]\n\n### Routing Recommendation\n**Route to:** [Team or queue]\n**Why:** [Brief reasoning]\n\n### Suggested Initial Response\n[Draft first response to the customer — acknowledge the issue,\nset expectations, provide workaround if available.\nUse the auto-response templates below as a starting point.]\n\n### Internal Notes\n- [Any additional context for the agent picking this up]\n- [Reproduction hints if it's a bug]\n- [Escalation triggers to watch for]\n```\n\n### 6. Offer Next Steps\n\nAfter presenting the triage:\n- \"Want me to draft a full response to the customer?\"\n- \"Should I search for more context on this issue?\"\n- \"Want me to check if this is a known bug in the tracker?\"\n- \"Should I escalate this? I can package it with \u002Fcustomer-escalation.\"\n\n---\n\n## Category Taxonomy\n\nAssign every ticket a **primary category** and optionally a **secondary category**:\n\n| Category | Description | Signal Words |\n|----------|-------------|-------------|\n| **Bug** | Product is behaving incorrectly or unexpectedly | Error, broken, crash, not working, unexpected, wrong, failing |\n| **How-to** | Customer needs guidance on using the product | How do I, can I, where is, setting up, configure, help with |\n| **Feature request** | Customer wants a capability that doesn't exist | Would be great if, wish I could, any plans to, requesting |\n| **Billing** | Payment, subscription, invoice, or pricing issues | Charge, invoice, payment, subscription, refund, upgrade, downgrade |\n| **Account** | Account access, permissions, settings, or user management | Login, password, access, permission, SSO, locked out, can't sign in |\n| **Integration** | Issues connecting to third-party tools or APIs | API, webhook, integration, connect, OAuth, sync, third-party |\n| **Security** | Security concerns, data access, or compliance questions | Data breach, unauthorized, compliance, GDPR, SOC 2, vulnerability |\n| **Data** | Data quality, migration, import\u002Fexport issues | Missing data, export, import, migration, incorrect data, duplicates |\n| **Performance** | Speed, reliability, or availability issues | Slow, timeout, latency, down, unavailable, degraded |\n\n### Category Determination Tips\n\n- If the customer reports **both** a bug and a feature request, the bug is primary\n- If they can't log in due to a bug, category is **Bug** (not Account) — root cause drives the category\n- \"It used to work and now it doesn't\" = **Bug**\n- \"I want it to work differently\" = **Feature request**\n- \"How do I make it work?\" = **How-to**\n- When in doubt, lean toward **Bug** — it's better to investigate than dismiss\n\n## Priority Framework\n\n### P1 — Critical\n**Criteria:** Production system down, data loss or corruption, security breach, all or most users affected.\n\n- The customer cannot use the product at all\n- Data is being lost, corrupted, or exposed\n- A security incident is in progress\n- The issue is worsening or expanding in scope\n\n**SLA expectation:** Respond within 1 hour. Continuous work until resolved or mitigated. Updates every 1-2 hours.\n\n### P2 — High\n**Criteria:** Major feature broken, significant workflow blocked, many users affected, no workaround.\n\n- A core workflow is broken but the product is partially usable\n- Multiple users are affected or a key account is impacted\n- The issue is blocking time-sensitive work\n- No reasonable workaround exists\n\n**SLA expectation:** Respond within 4 hours. Active investigation same day. Updates every 4 hours.\n\n### P3 — Medium\n**Criteria:** Feature partially broken, workaround available, single user or small team affected.\n\n- A feature isn't working correctly but a workaround exists\n- The issue is inconvenient but not blocking critical work\n- A single user or small team is affected\n- The customer is not escalating urgently\n\n**SLA expectation:** Respond within 1 business day. Resolution or update within 3 business days.\n\n### P4 — Low\n**Criteria:** Minor inconvenience, cosmetic issue, general question, feature request.\n\n- Cosmetic or UI issues that don't affect functionality\n- Feature requests and enhancement ideas\n- General questions or how-to inquiries\n- Issues with simple, documented solutions\n\n**SLA expectation:** Respond within 2 business days. Resolution at normal pace.\n\n### Priority Escalation Triggers\n\nAutomatically bump priority up when:\n- Customer has been waiting longer than the SLA allows\n- Multiple customers report the same issue (pattern detected)\n- The customer explicitly escalates or mentions executive involvement\n- A workaround that was in place stops working\n- The issue expands in scope (more users, more data, new symptoms)\n\n## Routing Rules\n\nRoute tickets based on category and complexity:\n\n| Route to | When |\n|----------|------|\n| **Tier 1 (frontline support)** | How-to questions, known issues with documented solutions, billing inquiries, password resets |\n| **Tier 2 (senior support)** | Bugs requiring investigation, complex configuration, integration troubleshooting, account issues |\n| **Engineering** | Confirmed bugs needing code fixes, infrastructure issues, performance degradation |\n| **Product** | Feature requests with significant demand, design decisions, workflow gaps |\n| **Security** | Data access concerns, vulnerability reports, compliance questions |\n| **Billing\u002FFinance** | Refund requests, contract disputes, complex billing adjustments |\n\n## Duplicate Detection\n\nBefore creating a new ticket or routing, check for duplicates:\n\n1. **Search by symptom**: Look for tickets with similar error messages or descriptions\n2. **Search by customer**: Check if this customer has an open ticket for the same issue\n3. **Search by product area**: Look for recent tickets in the same feature area\n4. **Check known issues**: Compare against documented known issues\n\n**If a duplicate is found:**\n- Link the new ticket to the existing one\n- Notify the customer that this is a known issue being tracked\n- Add any new information from the new report to the existing ticket\n- Bump priority if the new report adds urgency (more customers affected, etc.)\n\n## Auto-Response Templates by Category\n\n### Bug — Initial Response\n```\nThank you for reporting this. I can see how [specific impact]\nwould be disruptive for your work.\n\nI've logged this as a [priority] issue and our team is\ninvestigating. [If workaround exists: \"In the meantime, you\ncan [workaround].\"]\n\nI'll update you within [SLA timeframe] with what we find.\n```\n\n### How-to — Initial Response\n```\nGreat question! [Direct answer or link to documentation]\n\n[If more complex: \"Let me walk you through the steps:\"]\n[Steps or guidance]\n\nLet me know if that helps, or if you have any follow-up\nquestions.\n```\n\n### Feature Request — Initial Response\n```\nThank you for this suggestion — I can see why [capability]\nwould be valuable for your workflow.\n\nI've documented this and shared it with our product team.\nWhile I can't commit to a specific timeline, your feedback\ndirectly informs our roadmap priorities.\n\n[If alternative exists: \"In the meantime, you might find\n[alternative] helpful for achieving something similar.\"]\n```\n\n### Billing — Initial Response\n```\nI understand billing issues need prompt attention. Let me\nlook into this for you.\n\n[If straightforward: resolution details]\n[If complex: \"I'm reviewing your account now and will have\nan answer for you within [timeframe].\"]\n```\n\n### Security — Initial Response\n```\nThank you for flagging this — we take security concerns\nseriously and are reviewing this immediately.\n\nI've escalated this to our security team for investigation.\nWe'll follow up with you within [timeframe] with our findings.\n\n[If action is needed: \"In the meantime, we recommend\n[protective action].\"]\n```\n\n## Triage Best Practices\n\n1. Read the full ticket before categorizing — context in later messages often changes the assessment\n2. Categorize by **root cause**, not just the symptom described\n3. When in doubt on priority, err on the side of higher — it's easier to de-escalate than to recover from a missed SLA\n4. Always check for duplicates and known issues before routing\n5. Write internal notes that help the next person pick up context quickly\n6. Include what you've already checked or ruled out to avoid duplicate investigation\n7. Flag patterns — if you're seeing the same issue repeatedly, escalate the pattern even if individual tickets are low priority\n",{"name":5,"license":15,"metadata":33,"description":7,"argument-hint":40},{"author":34,"source":35,"source_url":36,"packaged-by":12,"packaged-on":37,"original-name":38,"upstream-commit":39},"Anthropic","anthropics\u002Fknowledge-work-plugins\u002Fcustomer-support\u002Fskills\u002Fticket-triage","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002F1c7187c4fc17feefa6cde39517f12dae1249e6c4\u002Fcustomer-support\u002Fskills\u002Fticket-triage\u002FSKILL.md","2026-09-25","ticket-triage","1c7187c4fc17feefa6cde39517f12dae1249e6c4","\u003Cticket or issue description>","main","7ed3b73314d5186120e8d4006febfd7e1c92cf08","skills\u002Fsupport-ticket-triage",0,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas","agpt.co","2026-11-10 22:38:50",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Significant-Gravitas\u002Fskills-catalog --skill support-ticket-triage",{"tool":55,"command":56},"bunx","bunx skills add Significant-Gravitas\u002Fskills-catalog --skill support-ticket-triage",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Significant-Gravitas\u002Fskills-catalog --skill support-ticket-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fsupport-ticket-triage\u002FSKILL.md",true,[63,69,73],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"ATTRIBUTION.md","REFERENCE","参考文档",2041,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fsupport-ticket-triage\u002FATTRIBUTION.md",{"path":70,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":16},"LICENSE","许可证",11358,{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002FCONNECTORS.md",1468,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fsupport-ticket-triage\u002Freferences\u002FCONNECTORS.md",[78,89,117,127,141,159],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":28},"01M6AD3S89TGF74S7MK4K5CGC7","workplace-memory-management","Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory\u002F directory for the full knowledge base.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fworkplace-memory-management\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fworkplace-memory-management\u002FSKILL.md",[],[86,87,27,26,23,88],"workplace memory management","memory","directory",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":110,"publishedAt":28},"01M6AD3F5X5DYW1BABD49BQKP8","website-seo-audit","Audit a website, investigate its real search opportunities, and deliver a short data-backed report on the few changes most likely to grow organic traffic that converts.","MIT","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-seo-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-seo-audit\u002FSKILL.md",[97,102,105],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":103,"categoryName":104,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[111,112,113,23,27,26,114,115,116],"website seo audit","audit","website","search","report","plugin",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":28},"01M6AD32RYMK03P50DM0T184NJ","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[125,126,26,23],"verification before completion","verification",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":28},"01M6AD2WSQG7BGPXA7XP4DFZX8","vendor-evaluation","Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-evaluation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-evaluation\u002FSKILL.md",[],[135,136,27,26,137,138,139,23,140],"vendor evaluation","negotiation","assessment","risk assessment","cost analysis","review",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":154,"publishedAt":28},"01M6AD2RBT6004C07RZRDSTA52","vendor-contract-status","Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FSKILL.md",[148,151],{"categoryNo":149,"categoryName":150,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":152,"categoryName":153,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000037","律师与法务",[155,156,23,157,27,158,26],"vendor contract status","status","storage","onboarding",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":28},"01M6AD2KPNXN5CNS3CA4FRWT97","user-cohort-analysis","Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fuser-cohort-analysis\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fuser-cohort-analysis\u002FSKILL.md",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000033","数据分析师",[170,171,26,23],"user cohort analysis","analytics"]