team-workload

team-workload is a skill for Claude Code from jonny-1812/corebee-mcp-skills. It costs 49 tokens per session (1,460 once invoked), scanned A, original, MIT.

A team-capacity and workload analysis skill for support or conversation teams. It shows assigned and unassigned conversations, agent availability, response performance, and workload balance.

In plain words
What is it for?
It helps view workload, identify agents with too many or too few open conversations, and rebalance assignments.
Why use it?
It makes overloaded or underused team members visible so work can be redistributed more evenly.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the corebee plugin — 10 skills, 4 commands, 4 agents, 3 hooks, 1 MCP server shipped together

Good fit It helps view workload, identify agents with too many or too few open conversations, and rebalance assignments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonny-1812/corebee-mcp-skills/team-workload
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jonny-1812/corebee-mcp-skills --skill team-workload
Clone the repo
git clone --depth 1 https://github.com/jonny-1812/corebee-mcp-skills

Made for: Claude Code.

Or install corebee, the plugin that ships this one along with the rest of its 10 skills, 4 commands, 4 agents, 3 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for team-workload

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/team-workload/github.svg)](https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/team-workload)
Your own site
<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/team-workload"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/team-workload/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for team-workload

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/team-workload"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/team-workload.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,460 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01460
Opus 5 $0.00024 $0.00730
Sonnet 5 $0.00010 $0.00292
Haiku 4.5 $0.00005 $0.00146

Measured 11d ago against content hash 3f8ad40f4035, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

team-workload scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/team-workload/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Team Workload

Analyze agent capacity, detect overload conditions, and rebalance conversation assignments to keep the team running smoothly.

Workflow Modes

View Workload (default)

Display the current workload distribution across the entire team.

  1. Fetch team members using list_team_members to get all agents, their roles, and online status
  2. Fetch open conversations using list_conversations with status: "open" to see all active work
  3. Count conversations per agent by grouping on the assignee field
  4. Count unassigned conversations separately
  5. Fetch agent performance data using get_agent_performance for each agent to add response time and resolution rate context
  6. Calculate the distribution ratio: each agent's share of total open conversations as a percentage
  7. Flag agents who exceed the overload threshold (12+ conversations)
  8. Present the workload table

Rebalance Queue

Redistribute conversations from overloaded agents to those with available capacity.

  1. Run the View Workload workflow to get current state
  2. Identify overloaded agents (12+ conversations) and underloaded agents (fewer than 6 conversations)
  3. For each overloaded agent, select conversations to reassign — prefer newer, lower-priority, and unresponded conversations
  4. Build a rebalance plan: which conversations move from which agent to which agent
  5. Present the rebalance plan to the user for confirmation
  6. On confirmation, execute reassignments using assign_conversation for each conversation
  7. Also assign any unassigned conversations to agents with the most available capacity
  8. Present a before-and-after summary showing the new distribution

Check Specific Agent

Show detailed workload and performance data for a single agent.

  1. Fetch team members using list_team_members to find the named agent
  2. Fetch open conversations using list_conversations with status: "open" and filter to those assigned to the agent
  3. Fetch the agent's performance data using get_agent_performance
  4. Optionally fetch overall metrics using get_metrics for comparison
  5. Present the agent detail card with their conversations, performance stats, and capacity status

Read the full file on GitHub · 124 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 124 lines · 49 tokens per session scan A 3f8ad40f4035

Subscribe to this mod's changes

team-workload is a skill published in the GitHub repository jonny-1812/corebee-mcp-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,460 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

Zendesk Automation

Automate customer support workflows with Zendesk ticket management, routing, and analytics.

claude-office-skills/skills · 19 tokens

customer-support

Use when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or escalation with a handoff packet. NOT the help-center article it links to (that is technical-writing), a win-back program (retention), or the…

ericrisco/rsc-harness · 90 tokens

customer-support-expert

Build comprehensive customer support systems including ticketing, knowledge management, SLA tracking, and customer satisfaction analytics. Use when the user mentions helpdesk or service desk, ticketing, SLA targets, knowledge bases, escalation workflows, CSAT/NPS, or customer success operations.

personamanagmentlayer/pcl · 58 tokens

deskcrew-bounty-hunter

Earn USDC by answering bounty support tickets on DeskCrew's open board. Read the board free, buy ticket context over x402, draft an answer, submit it, and get paid 85% of the bounty when a human approves. Pays out on Base, Polygon, Avalanche, Sei, or Solana; on Solana the agent needs zero SOL. Since 08-2026 the wallet…

webmilmind1/deskcrew-mcp · 0 tokens

deskcrew-support

Run a customer support desk on DeskCrew. Read new tickets, answer from the knowledge base, and file replies for human approval. Use when handling customer support. Agents can also create and run their own bounty board over x402 with no account (the wallet that pays createboard owns it) and pay answering agents 85% on…

webmilmind1/deskcrew-mcp · 72 tokens

deskcrew-board-owner

Run your own USDC bounty board and pay AI agents to answer your questions. One x402 payment creates the board (no account, the paying wallet owns it), USDC deposits fund tasks, and approving an answer pays the winning agent 85% automatically on Base, Polygon, Avalanche, Sei, or Solana. Use when asked to delegate work…

webmilmind1/deskcrew-mcp · 93 tokens