跳到正文
cccskills
免费在 GitHub 公开

triage-superhuman-inbox

Sort a Superhuman inbox into messages needing a reply, waiting for others, useful information, and noise. Receive a clear attention list, then apply requested actions such as archiving, labeling, reminders, or unsubscribing.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Work through a Superhuman inbox — sort what is there into needs a reply, waiting on someone else, worth knowing, and noise, then archive, star, label, remind, or unsubscribe only as the user directs. Use when the user asks what needs their attention, what they are waiting on, to triage or clean up their inbox, or to deal with newsletters and notifications.

实测评分 未实测

查看安装方法

适用场景

  • Finding messages that need a reply
  • Reviewing requests awaiting a response
  • Sorting newsletters and notifications
  • Setting reminders for selected threads

包含的文件(1)

  • SKILL.md4.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Sort first, act second

Triage is a reading job with a short list of actions at the end. Read enough of each thread to know what it asks of the user, group the inbox by what happens next, and change the mailbox only where the user said to.

1. Scope the sweep

list_accounts first. When the user named an account, or more than one is linked, every call that follows carries that account's acting_email, reads and changes alike: a call without it acts on the default account, so a sweep of the wrong mailbox looks exactly like a successful sweep. Then list_splits: splits carry thread and unread counts, so you can say "Important has 14 unread, Other has 212" before reading anything. Triage the splits the user cares about (Important, VIP, Team, a support split) one at a time with list_threads, and leave Other and the notification splits for a cleanup pass the user asks for. is_unread narrows a split, but split ignores the date filters and sort only orders the returned page, so a time window is yours to enforce: page with cursor and compare each thread's timestamp against the window. An older thread on a page does not end the sweep; later pages can still hold threads inside it.

2. Read enough to classify

The listing's snippet is the latest message, which is often the user's own reply. Open threads where the ask is unclear with get_thread and read the last exchange. Sort each thread into one of four groups:

  • Needs a reply from the user: a question or request addressed to them, with no answer from them after it.
  • Waiting on someone else: the user wrote last, or asked for something that has not come back.
  • Worth knowing: FYI, decisions made elsewhere, receipts.
  • Noise: newsletters, automated notifications, cold outreach.

Participants and dates decide the group, not the sender's name or the subject line. A thread where the user replied last is waiting only when that reply asked for something; a closing thanks, or an answer that settled the question, is done, however urgent the subject reads.

3. Report before changing anything

One line per thread in the first two groups: who, what they want, how old, and the link https://mail.superhuman.com/<account email>/thread/<thread id>. Oldest first in "needs a reply", because that is the order the user is behind in. Summarize the other two groups by count and sender. Then stop, unless the user already said what to do with each group.

4. Act only as directed, and against the thread's last message

update_thread archives (mark_done), stars, marks read, moves a thread between Important and Other, and adds or removes labels. It needs the thread's last_message_id from get_thread, so a reply that landed meanwhile is not archived unseen. Labels must already exist; check list_labels. Its move_to_folder never points at Trash: that is how update_thread can trash a thread, and trashing is not triage.

create_or_update_reminder is Superhuman's Remind Me: by default it removes the thread from the inbox until remind_at, and it cancels itself if someone replies first. Pass mark_done: false when the user wants the thread to stay visible. A thread holds one reminder, so setting another reschedules it.

unsubscribe uses the list's own unsubscribe header. Leave also_block and also_trash off unless the user asked for them, and never block a domain over one message: also_domain silences everyone at that company.

Marking spam and trashing are not triage, and neither mark_spam nor trash_thread is granted here, so each asks before it runs. If the user wants a thread gone, name it and let them confirm.

Anti-patterns

  • Archiving on the way through. A thread marked done leaves the inbox; triage reports, the user decides.
  • Calling a thread urgent because the sender is. Age and who spoke last decide where it goes.
  • Reading Other before Important. Hundreds of notifications are not where the user's day is.
  • Treating the snippet as the ask. It is the newest message, not the question.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

10x

免费

Review how you use Superset and identify unused features that fit your workflow. Get a short list of suggestions, learn about each option, and set up selected features such as scheduled agents, parallel workspaces, or shared tasks.

中文简介正在准备中。当前显示英语简介。

  • Find unused Superset features worth exploring
  • Set up scheduled agent tasks
  • Start parallel work in separate workspaces
superset-sh/superset1.6万2026年10月23日 更新

automate

免费

Set up recurring tasks in Superset with an agent prompt, a schedule or event trigger, and a chosen execution workspace. After explicit confirmation, create the automation, check its saved settings, and review a real first run.

中文简介正在准备中。当前显示英语简介。

  • Scheduling a daily or weekly agent task
  • Starting agent work when a GitHub pull request opens
  • Triggering tasks from selected Slack reactions
superset-sh/superset1.6万2026年10月23日 更新

browser

免费

Browse pages, click controls, fill fields, and inspect screenshots or console messages through Superset's browser pane. Use it to preview a running web app, check interface behavior, and work through browser tasks in a visible session.

中文简介正在准备中。当前显示英语简介。

  • Preview a locally running web app
  • Capture screenshots of a page
  • Inspect console errors
superset-sh/superset1.6万2026年10月23日 更新

Build Stripe payments, subscriptions, and invoicing using verified documentation and API parameter definitions. The skill guides product selection, sandbox testing, and webhook handling, where server notifications determine payment and subscription state.

中文简介正在准备中。当前显示英语简介。

  • Choose Stripe products for payments or recurring billing
  • Implement Checkout or invoice flows
  • Investigate Stripe code that compiles but behaves incorrectly
superset-sh/superset1.6万2026年10月23日 更新

Verify desktop UI changes through the Chrome DevTools Protocol, a connection for controlling the running app. Reproduce the user’s actual steps and compare screenshots, measured state, and console errors to establish evidence before and after a fix.

中文简介正在准备中。当前显示英语简介。

  • Reproducing reported bugs in the running app
  • Comparing UI behavior before and after a fix
  • Checking state across navigation and reopening
superset-sh/superset1.6万2026年10月23日 更新

ci-triage

免费

Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.

中文简介正在准备中。当前显示英语简介。

  • Investigating failed PR checks
  • Separating intermittent test failures from code defects
  • Checking whether the base branch already fails
superset-sh/superset1.6万2026年10月23日 更新

查看 superset-sh 的全部技能

报告此技能的问题