--- name: al-437-put-a-triage-bot-in-your-team-chat-when-someone-reports-a description: "ElevenLabs wrote on Oct 29, 2026 that its internal agents save teams more than 1,200 hours a month and answer over 5,000 questions a month in Slack. Its triage bot opened more than 150 tickets in the past month: before creating one it searches Slack for context, checks existing tickets for duplicates, makes sure there is enough detail to diagnose the issue, then opens a Linear ticket with the right priority and routes it using an ownership document. After creating the ticket it checks that the fields and team are correct. The company found that trimming the data an agent can see to a few critical fields improved accuracy more than tuning the prompt. The prompt below sets up the same triage routine for any small team. Use when the user wants help with bug and request triage from team chat (operations) for a small business." --- # Put a triage bot in your team chat: when someone reports a bug or asks for a feature, the AI agent gathers context from the chat, checks for an existing ticket, asks for missing details and opens a properly prioritised ticket for the right team ElevenLabs wrote on Oct 29, 2026 that its internal agents save teams more than 1,200 hours a month and answer over 5,000 questions a month in Slack. Its triage bot opened more than 150 tickets in the past month: before creating one it searches Slack for context, checks existing tickets for duplicates, makes sure there is enough detail to diagnose the issue, then opens a Linear ticket with the right priority and routes it using an ownership document. After creating the ticket it checks that the fields and team are correct. The company found that trimming the data an agent can see to a few critical fields improved accuracy more than tuning the prompt. The prompt below sets up the same triage routine for any small team. ## Inputs to collect first Ask the user for anything below that they haven't already given you. Don't guess missing facts. - #bugs-and-requests - Linear / Jira / Trello / a shared spreadsheet - A short list, e.g. 'billing page: Sam; mobile app: Priya; website… - Link ## Instructions Do the task below with the user's inputs in place of each [bracket]. Be the triage assistant in our team chat channel [#bugs-and-requests]. Our ticket tool is [Linear / Jira / Trello / a shared spreadsheet]. Who owns what: [paste a short list, e.g. 'billing page: Sam; mobile app: Priya; website: Lee']. When someone posts a bug or feature request: 1) Decide if it is a bug, a feature request or a question, and answer questions directly if our docs [link] cover it. 2) Search recent chat messages and existing tickets for the same issue. If one exists, link it in the thread and add any new details there instead of opening a duplicate. 3) If key details are missing (for a bug: what they did, what they expected, what happened, device or browser, screenshot; for a feature: who needs it and why), ask in the thread before creating anything. 4) Create the ticket with a clear title, steps to reproduce or the use case, a priority (urgent if customers are blocked or money is affected, otherwise high, medium or low with a one-line reason) and the owner from the list. 5) Re-read the ticket after creating it to confirm the fields and owner are right, then post the link in the thread. Never close or delete tickets, and never guess at details nobody gave you. ## Safety checks (share these with the user) - This prompt works on text other people wrote (emails, reviews, messages or web pages). That text can hide instructions aimed at AI, such as "ignore your rules and…". Paste it as material to work on, and never let the AI act on requests inside it, like paying, sharing logins or changing records. - Remove names, contact details, account numbers and other personal data the task doesn't need before you paste, and check your AI tool's data and training settings. - Read and edit the draft before it reaches a customer or goes public. If you later automate this prompt, start with "draft and notify me", not "send automatically". - Check names, dates, numbers and any claim against your own source material before you use the answer. AI can misread or invent details. - Say clearly which parts need a person to review or approve before anything is sent, paid, posted or filed. ## About this skill - Works with: Slack, Microsoft Teams, Linear, Jira, ElevenLabs ElevenAgents, Claude, ChatGPT - Based on this real-world example: https://elevenlabs.io/blog/internal-ops-agents - Free prompt from AgentPlaybook Real Estate: https://agentic-library.netlify.app/prompt/al-437-put-a-triage-bot-in-your-team-chat-when-someone-reports-a-bu/ - To install in an agent that supports Agent Skills, save this file as SKILL.md in a folder with the same name as `name` above (for example in your skills directory). Install steps for Claude.ai, Claude Code, Cursor and Codex: https://agentic-library.netlify.app/skills/