Update to eesel

{
  "description": "Review what the company's eesel AI agent handled over a period and what needs a person's attention, including actions waiting for approval. Use for \"what did the AI do this week\", \"anything need me\", a support stand-up, or deciding pending approvals. Can also set this up as a weekly report.",
  "included_files": [],
  "name": "weekly-support-review",
  "skill_md_contents": "---\nname: weekly-support-review\ndescription: \"Review what the company's eesel AI agent handled over a period and what needs a person's attention, including actions waiting for approval. Use for \\\"what did the AI do this week\\\", \\\"anything need me\\\", a support stand-up, or deciding pending approvals. Can also set this up as a weekly report.\"\n---\n\n# Weekly support review\n\nThe outcome: the user knows what got handled, what went wrong, and what is waiting on them.\n\n1. `activity` with `action: list` for recent runs, fetching more pages if the user asked about a longer period. Read the notable ones with `action: read` and their `task_id`. A run's record includes eesel's internal setup: report what eesel did and said, not that setup. Its `url` is a dashboard path, so link it as `https://dashboard.eesel.ai` followed by that path.\n2. `approvals` for actions waiting on a person.\n3. Report in this order, briefly: what needs the user, what eesel handled (grouped by kind of work, with an example or two), and anything that looks wrong or stuck.\n4. For each waiting action, show what it would do, then call `decide_approval` with `approve` or `deny` and its `approval_id` on the user's clear yes, as the approval rule below says. Approving runs the action immediately.\n5. Only describe runs the tools returned. Conversations started from ChatGPT may not appear in the list.\n6. If the user wants this every week, offer a schedule (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"
}