Update to eesel

{
  "description": "Work with eesel, the AI teammate the user's company has hired, when the user addresses eesel by name or refers to their eesel workspace. Do not use for general questions that are not about the user's own company or eesel workspace.",
  "included_files": [],
  "name": "eesel",
  "skill_md_contents": "---\nname: eesel\ndescription: \"Work with eesel, the AI teammate the user's company has hired, when the user addresses eesel by name or refers to their eesel workspace. Do not use for general questions that are not about the user's own company or eesel workspace.\"\n---\n\n# eesel\n\neesel is the company's AI teammate. The same teammate answers customers in the helpdesk, works with the team in Slack and the eesel dashboard, and is reachable here.\n\nFor a specific outcome, use the matching skill: reply-to-a-customer, answer-from-company-knowledge, clear-the-support-backlog, automate-support-tickets, set-up-ai-support, find-what-customers-ask-about, write-help-center-articles, fix-a-wrong-ai-answer, weekly-support-review.\n\nFor anything else, talk to eesel through `chat`. The other tools are for raw readouts: `status`, `integrations`, `activity`, `approvals`, `instructions`, `automations`, `files`, `billing`, and `invite` to add a colleague.\n\nThe user's eesel role decides what they can change. If a write tool refuses because they have view-only access, say so and suggest someone with edit access. Writes follow the workspace's approval settings, so a change can come back as waiting rather than done: report which. Only report what a tool returned.\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"
}