Spot overloaded and idle agents in a Zendesk group

**Objective:** Report the current workload of each agent in group `{group-name}` and flag imbalance.

**Step 1: Resolve the group**

Call `zendesk-get-group` with group-name `{group-name}` and deleted false. If nothing matches, retry with group-name.contains. If none or several match, list them and stop.

**Step 2: List the agents**

Call `zendesk-get-group-member` with the group-id. Keep user-id, user-name, user-email and user-role for each member.

**Step 3: Count each agent's work**

For each member (at most 25):

* Call `zendesk-get-ticket` with assignee-name set to the member's user-name, once for status open and once for status pending, max-records 200. Count urgent and high priority tickets and any past due-date.
* Call `zendesk-get-skipped-ticket` with user-id set to the member's user-id and created.from set to today minus 14 days (YYYY-MM-DD). Count skips and note the common skip-reason values.

Then call `zendesk-get-ticket` with group-name set to the group and status new to count unassigned new work waiting in the queue.

**Step 4: Report**

1. A table: agent name, open, pending, urgent+high, overdue, skips in 14 days.
2. The group total and the unassigned new count.
3. Imbalance: any agent carrying more than twice the group median of open tickets, and any agent with no open work.
4. Skips: agents who skip often, with the reasons, as a signal of tickets outside their skills.
5. Rebalancing suggestions naming specific ticket-ids that could move.

**Rules & Guidelines:**

* This prompt is read-only. Do NOT call `zendesk-update-ticket`, `zendesk-add-group-member`, `zendesk-update-group` or any other add, update or make tool. Suggest moves; do not make them.
* Tickets are matched by assignee name; if two agents share a name, say the counts may be merged.

**Validation:**

* If the group has no members, say so and stop.
* If a member has role end-user, skip them and note it; only agents and admins take tickets.