Update to eesel

{
  "description": "Find the most common questions, complaints, trends and customer sentiment in the company's recent support tickets. Use when the user wants to know what customers are contacting support about, why ticket volume went up, why customers are unhappy, which issues keep recurring, or what to fix or document next.",
  "included_files": [],
  "name": "find-what-customers-ask-about",
  "skill_md_contents": "---\nname: find-what-customers-ask-about\ndescription: \"Find the most common questions, complaints, trends and customer sentiment in the company's recent support tickets. Use when the user wants to know what customers are contacting support about, why ticket volume went up, why customers are unhappy, which issues keep recurring, or what to fix or document next.\"\n---\n\n# Find what customers ask about\n\nThe outcome: the handful of topics driving support, with real examples, so the user knows what to fix, document or automate.\n\n1. Agree the window and scope with the user (last week, last month, one product, one tag).\n2. Ask eesel through `chat` to look across those tickets and group them by topic, with a rough count and an example for each.\n3. eesel can only look across tickets that have been downloaded into eesel. If it says it has none, or only old ones, use set-up-ai-support to download recent tickets first.\n4. Relay eesel's findings. Give numbers only as eesel stated them, and say when they are estimates. If eesel only saw part of the period, say so.\n5. If the user wants to act on a topic, write-help-center-articles and automate-support-tickets cover the usual next steps.\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"
}