inbox-triage

inbox-triage is a skill for Claude Code from jonny-1812/corebee-mcp-skills. It costs 64 tokens per session (1,340 once invoked), scanned A, original, MIT.

A support-inbox review workflow that groups open conversations by urgency and recommends what should happen next.

In plain words
What is it for?
It helps find urgent and unassigned tickets, inspect their message threads, assess topic and complexity, check team availability, balance workload, and recommend or perform assignments.
Why use it?
An open-ticket queue can hide urgent or unassigned requests, especially when workload is uneven. This gives a quick overview or reviews selected conversations in more detail.

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 find urgent and unassigned tickets, inspect their message threads, assess topic and complexity, check team availability, balance workload, and recommend or perform assignments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonny-1812/corebee-mcp-skills/inbox-triage
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 inbox-triage
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 inbox-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/inbox-triage/github.svg)](https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/inbox-triage)
Your own site
<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/inbox-triage"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/inbox-triage/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 inbox-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/inbox-triage"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/inbox-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,340 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.00064 $0.01340
Opus 5 $0.00032 $0.00670
Sonnet 5 $0.00013 $0.00268
Haiku 4.5 $0.00006 $0.00134

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

Security

Grade A, and why

inbox-triage 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 12d 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/inbox-triage/SKILL.md · 107 lines

How it starts

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

Inbox Triage

Automatically review and prioritize the support queue by analyzing open conversations, team availability, and workload distribution.

Workflow Modes

Quick Scan (default)

A fast overview of the inbox state. Fetches open conversations and groups them by urgency without reading individual message threads.

  1. Fetch open conversations using list_conversations with status: "open"
  2. Fetch team members using list_team_members to check availability
  3. Group conversations by priority bucket (Critical, Needs Response, In Progress)
  4. Present the summary with counts and top items per bucket

Deep Review

Reads into each unassigned or stale conversation to understand context and recommend specific actions.

  1. Fetch open conversations using list_conversations with status: "open"
  2. Fetch team members using list_team_members to check availability and current load
  3. For each unassigned or high-priority conversation, use get_conversation to read the full message thread
  4. Analyze sentiment, topic, and complexity of each conversation
  5. Present a detailed prioritized summary with per-conversation action recommendations

Auto-Assign

Automatically assigns unassigned conversations to available agents based on workload and availability. Requires explicit user confirmation before executing assignments.

  1. Fetch open conversations using list_conversations with status: "open"
  2. Fetch team members using list_team_members to check availability, roles, and current assignment counts
  3. For each unassigned conversation, determine the best agent match based on lowest current load and online status
  4. Present the proposed assignment plan and ask the user to confirm
  5. On confirmation, execute assignments using assign_conversation for each conversation
  6. Report results: how many assigned, to whom, and any that could not be assigned

Prioritization Rules

  • Critical: High priority AND unassigned, OR any conversation breaching the SLA threshold — needs immediate attention
  • Needs Response: No activity for sla_threshold_hours (default: 4 hours) — going stale
  • In Progress: Assigned and recently active — being handled
  • Waiting on Customer: Agent responded, awaiting customer reply — monitor only

Read the full file on GitHub · 107 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. 12d ago First seen · 107 lines · 64 tokens per session scan A a5d924eaf630

Subscribe to this mod's changes

inbox-triage is a skill published in the GitHub repository jonny-1812/corebee-mcp-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,340 once invoked, about $0.0003 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-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-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-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