agentsclimarketplace

Cowork inbox triage

Skill bg-szy/TOP-SKILLS/skills/claude-skills/cowork-inbox-triage

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install
npx -y skills add bg-szy/TOP-SKILLS --skill cowork-inbox-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Daily inbox triage using Cowork's email write tools (Microsoft 365 or Gmail) -- classifies unread mail, drafts replies in your voice, flags what needs a decision, and schedules follow-ups. Built to run as a recurring Cowork scheduled task.

SKILL.md

3.2 KB, 670 tokens by cl100k_base, as published. Nobody here has run it

Cowork Inbox Triage

Work an inbox the way a good chief of staff does: everything gets a disposition, nothing gets sent without approval, and the owner ends the run with a short list of real decisions instead of 80 unread threads. Uses the connected mail tools (Microsoft 365 or Gmail MCP connectors) for reading, labeling, and drafting.

Setup

On first run, learn the owner's voice: read 10-15 sent replies and note greeting style, sign-off, sentence length, and formality. Store the profile in the conversation and reuse it for every draft. Ask once which categories matter (default set below) and what the auto-archive rules are.

Workflow

  1. Sweep. Pull unread and flagged threads from the last cycle (default: 24 hours). Group by thread, not message.
  2. Classify every thread into exactly one bucket:
    • NEEDS DECISION -- only the owner can answer (pricing, commitments, personnel)
    • DRAFT READY -- routine reply Claude can write for approval
    • WAITING ON THEM -- owner already replied; schedule a follow-up check
    • FYI -- no response needed; summarize in the digest
    • NOISE -- newsletters, notifications, cold outreach; label/archive per the standing rules
  3. Draft. For every DRAFT READY thread, write the reply in the owner's voice as a draft -- never send. Keep drafts shorter than the email being answered.
  4. Follow-ups. For WAITING ON THEM threads past their expected response window (default 3 business days), draft a polite bump. For threads with dates in them, propose calendar holds via the calendar write tools.
  5. Digest. Post one summary: decisions needed (with one-line context and a recommended answer each), drafts awaiting approval, follow-ups queued, and a one-line count of what was archived.

Rules

  • Never send email. Create drafts only; the human sends.
  • Never archive anything that mentions money, contracts, legal matters, or a specific person's problem -- misclassified noise is recoverable, a missed client email is not.
  • A recommended answer accompanies every NEEDS DECISION item. Surfacing a question without a recommendation is half the job.
  • Quote the sender's actual ask in the digest -- do not paraphrase requests into vagueness.
  • Respect confidentiality: HR, health, and personal matters get flagged privately, never summarized in a shared channel.
  • If the connector lacks write scope, degrade gracefully: produce the digest and paste-ready reply texts instead of drafts.

Scheduled Mode

As a Cowork scheduled task (weekday mornings), run the full workflow unattended in a cloud session and deliver the digest before the workday starts. Track threads across runs so a bump is never drafted twice for the same silence.

Quick Commands

  • "Triage my inbox" -- full run, last 24h
  • "Catch me up" -- sweep and digest only, no drafts
  • "Draft replies to everything easy" -- classification + drafts only
  • "Who am I waiting on?" -- the WAITING ON THEM ledger with days elapsed

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most debug triage skills give in 670 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

  • Investigate root cause before proposing any fixin 102 of 839, across 67 files
  • Read error messages completelyin 89 of 839, across 49 files
  • Create a failing test case before fixingin 84 of 839, across 46 files
  • Reproduce the issue consistentlyin 82 of 839, across 41 files
  • Change one variable at a timein 82 of 839, across 42 files
  • Check recent changesin 74 of 839, across 36 files
  • Write the regression test before fixingin 74 of 839, across 40 files
  • Fix the root cause not the symptomin 60 of 839, across 45 files
  • Implement a single fix at a timein 59 of 839, across 20 files
  • Trace data flow backward to the sourcein 50 of 839, across 20 files
  • Remove all debug instrumentationin 49 of 839, across 13 files
  • Form a single hypothesisin 48 of 839, across 18 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.