Update to eesel

{
  "description": "Work through support tickets already sitting in the queue: sort them, tag or route them, and draft replies, using the company's helpdesk and past answers. Use when the user is behind on tickets, wants the queue triaged, or asks for help getting through open or overdue tickets.",
  "included_files": [],
  "name": "clear-the-support-backlog",
  "skill_md_contents": "---\nname: clear-the-support-backlog\ndescription: \"Work through support tickets already sitting in the queue: sort them, tag or route them, and draft replies, using the company's helpdesk and past answers. Use when the user is behind on tickets, wants the queue triaged, or asks for help getting through open or overdue tickets.\"\n---\n\n# Clear the support backlog\n\nThe outcome: a smaller queue, with the easy tickets handled and the hard ones flagged for a person.\n\n1. Agree the scope with the user: which tickets (open, overdue, a tag, a view), and what eesel may do to them (draft replies, tag, route). Drafting is a safe default. Sending needs the user to say so.\n2. Hand eesel the job through `chat` in one message with that scope.\n3. Big jobs take a while. Tell the user eesel is on it, and collect the result when they ask, as described below.\n4. Report what eesel did as it reported it: how many tickets it touched, what it did to them, and which ones it left for a person and why.\n5. If the user wants that kind of ticket handled as it arrives from now on, see automate-support-tickets.\n\n## Working with eesel\n\n- eesel is the company's AI teammate. It works from the company's connected helpdesk, help center, docs and past tickets, so its answers follow this company's policies and tone, not general best practice.\n- Ask it through `chat`, in the user's words, with every specific they gave. Relay its reply faithfully: don't rewrite it into your own answer or add facts it didn't give.\n- Pass the reply's `task_id` back on follow-ups about the same thing. If a reply says eesel is still working, tell the user it is on it, and collect the result with `chat` and only that `task_id` when they ask. Don't poll in a loop. If it is still working after three collection attempts, call `status`: if the trial has ended or credit has run out, tell the user that is why.\n- If a reply says an action is waiting for approval, show the user what it would do. Call `decide_approval` only on the user's clear yes. A clear \"approve all\" covers only the actions they have just been shown.\n- If eesel has no helpdesk or knowledge connected yet, use set-up-ai-support first.\n- Never ask the user to paste passwords or API keys into this conversation.\n"
}