本文へ移動
cccskills
無料GitHub で公開

email-triage

Classify a batch of emails into action categories (reply now, reply later, archive, delete, unsubscribe) and surface unsubscribe candidates. Use after a busy week, running inbox zero, or triaging email overload.

インストール方法を見る

含まれるファイル(4)

  • SKILL.md3.7 KB
  • assets/gmail_filter_template.md2.3 KB
  • references/inbox_zero_method.md3.7 KB
  • scripts/email_classifier.py6.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Email Triage

Classify a batch of email subjects + senders into action buckets and surface inbox-zero candidates.


Keywords

email, inbox, inbox zero, triage, unsubscribe, mailing list, mailbox, gmail, outlook, productivity


Clarify First

Before triaging, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Inbox export fields — subject, sender, snippet drive classification accuracy; missing columns degrade the buckets
  • Priority / VIP senders — who always routes to reply_now regardless of content
  • Unsubscribe tolerance — purge all marketing vs keep newsletters you value; sets how aggressive the unsubscribe/delete buckets are

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.


Quick Start

  1. Export inbox to CSV with columns: subject,sender,snippet,received_at
  2. Run: python scripts/email_classifier.py inbox.csv
  3. Review action buckets; act on each in order

Core Workflows

Workflow 1: Weekly Inbox Triage

  1. Export the past week's inbox
  2. Run classifier
  3. Action in order: reply-now → reply-later (move to follow-up folder) → archive → unsubscribe → delete
  4. Apply Gmail filters (see assets/gmail_filter_template.md) so future similar emails route automatically

Time Estimate: 30-45 minutes for a busy week.

Workflow 2: Unsubscribe Pass

  1. Run classifier; review unsubscribe candidates
  2. Unsubscribe in batch (most senders honor unsubscribe links within ~10 days)
  3. For senders that don't honor, set Gmail filter to auto-delete

Time Estimate: 15 minutes per pass.

Workflow 3: Inbox-Zero Reset

  1. Apply the full inbox-zero method from references/inbox_zero_method.md
  2. Move every email older than 30 days to archive (you'll find 1% later via search)
  3. Triage the remaining recent emails using the classifier

Time Estimate: 1-2 hours one-time; then 20 min/week to maintain.


Tools

email_classifier.py

Classifies email rows into action buckets using rule-based pattern matching on sender domain, subject line, and snippet.

python scripts/email_classifier.py inbox.csv
python scripts/email_classifier.py inbox.csv --json

Action buckets:

  • reply_now — direct addressing, time-sensitive language, named-person sender
  • reply_later — informational threads, longer non-urgent
  • archive — receipts, confirmations, completed transactions
  • unsubscribe — newsletters, marketing, promotional
  • delete — spam patterns, low-signal senders
  • review — couldn't classify confidently

Reference Guides

  • references/inbox_zero_method.md — Method, daily routine, common pitfalls

Templates

  • assets/gmail_filter_template.md — Common Gmail filter recipes for the action buckets above

Best Practices

  • The 2-minute rule: if a reply takes < 2 minutes, do it now.
  • Don't archive instead of unsubscribing. Recurring senders compound — kill the source.
  • Process in batches. Constant inbox checking destroys focus more than email itself.
  • Inbox is not a to-do list. Move action items to a real task tool.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

Design and analyze A/B tests: sample size, test duration, and statistical significance for conversion experiments. Use when setting up an A/B test, calculating sample size, designing an experiment, or analyzing results.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

Design and run statistically rigorous A/B tests and experiments. Use when planning experiments, calculating sample sizes, designing test variants, selecting metrics, analyzing results, or when someone says "let's test that."

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

Sales execution across pipeline, discovery, demos, negotiation, and closing. Use when qualifying opportunities, running MEDDIC discovery, building account plans, handling objections, structuring proposals, or forecasting pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

Design ad creative across Google, Meta, LinkedIn, Twitter/X, and TikTok with platform format specs, headline formulas, and A/B testing. Use when writing ad copy, generating headline variations, creating ad sets, or validating creative.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

aeo

無料

Answer Engine Optimization (AEO): optimize content to be cited by LLMs (ChatGPT, Claude, Perplexity, Gemini) in their answers. Use when designing content for LLM citation, auditing citability, or structuring Q&A schema.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

borghei のスキルをすべて見る

このスキルの問題を報告する