Update to eesel

{
  "description": "Have new customer support tickets answered, drafted, tagged, routed or handed off to a person automatically as they arrive, or run a recurring support task on a schedule. Use when the user wants to stop handling repetitive questions like order-status emails by hand, or wants AI to reply to new tickets. Do not use for tickets already in the queue (clear-the-support-backlog), a recurring review of the AI's work (weekly-support-review), or work unrelated to support.",
  "included_files": [],
  "name": "automate-support-tickets",
  "skill_md_contents": "---\nname: automate-support-tickets\ndescription: \"Have new customer support tickets answered, drafted, tagged, routed or handed off to a person automatically as they arrive, or run a recurring support task on a schedule. Use when the user wants to stop handling repetitive questions like order-status emails by hand, or wants AI to reply to new tickets. Do not use for tickets already in the queue (clear-the-support-backlog), a recurring review of the AI's work (weekly-support-review), or work unrelated to support.\"\n---\n\n# Automate support tickets\n\nThe outcome: repetitive tickets handled without anyone touching them, in a way the team trusts.\n\n## Look first\n\n- `automations` with no arguments lists the workspace's schedules and webhook automations.\n- `automations` with `integration_key` (for example `zendesk`) lists the events that app offers. That is what can be switched on, not what is on, and it needs the app fully connected. Check `status` first and use set-up-ai-support if it isn't.\n\n## When a new ticket arrives\n\n1. Agree with the user which tickets and what eesel should do: draft a reply for a person to check, reply directly, or tag and route. Suggest starting with drafts, so the team can see eesel's answers before they go to customers.\n2. Pick the `trigger_key` from the list, then `manage_automations` with `action: enable` and `instructions` saying what eesel should do.\n3. Tell the user in plain words what will set it off, and what it excludes when that matters (for example \"new tickets only, not replies on existing ones\").\n\n## On a schedule\n\n`manage_automations` with `action: create`, a short `title`, a `prompt` written as the job itself, and a `cron` and `timezone`. Confirm the user's timezone and read the schedule back in words. Offer `action: run` with the new `trigger_id` so they see one run now.\n\n## Changing one\n\nConfirm with the user first. Pause an event automation with `action: disable`, its `integration_key` and `trigger_key`, and a schedule with `action: update`, its `trigger_id` and `enabled: false`. Only schedules can be deleted, with `action: delete`, and that cannot be undone.\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"
}