[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C22DRWVQZ7QSA2RYAM99YW":3,"skill-same:01M6C22DRWVQZ7QSA2RYAM99YW":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":25,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":13,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6C22DRWVQZ7QSA2RYAM99YW","inbox-triage",null,"Runs a full inbox triage using the knowledge base created by the 'inbox-setup' skill. Light-intake by design (most invocations skip questions and run with KB-default preferences); asks at most 2 grill-me override questions when invocation is outside normal cadence or includes category-skip intent. Searches recent emails, classifies them via the user's taxonomy, researches new senders, generates recommendations, drafts replies (NEVER sends), delivers a report in the user's preferred format, and updates the knowledge base with learnings. Designed to run on a recurring schedule (1-3x daily) or on demand. Use when the user wants their inbox processed, in any variation (e.g., 'triage my inbox', 'inbox triage', 'check my email', 'run email triage', 'process my inbox', 'what's new in my email', 'handle my email', 'email triage'). Requires the inbox-setup skill to have been run first.","mne20114-hash\u002Fgest35bi","mne20114-hash","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224168109?v=4","01M6C0JCR7334CZ39YWTZXX2NG","01M6C0JCWN0NBWMQTW1CPG2Z4G",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-triage\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"triage","inbox triage","inbox","use","design","kb","process","recurring","check","schedule","format","preferences","knowledge","taxonomy","first","email","file","intake","report","run","2026-11-10 10:12:30",false,"---\nname: inbox-triage\ndescription: \"Runs a full inbox triage using the knowledge base created by the 'inbox-setup' skill. Light-intake by design (most invocations skip questions and run with KB-default preferences); asks at most 2 grill-me override questions when invocation is outside normal cadence or includes category-skip intent. Searches recent emails, classifies them via the user's taxonomy, researches new senders, generates recommendations, drafts replies (NEVER sends), delivers a report in the user's preferred format, and updates the knowledge base with learnings. Designed to run on a recurring schedule (1-3x daily) or on demand. Use when the user wants their inbox processed, in any variation (e.g., 'triage my inbox', 'inbox triage', 'check my email', 'run email triage', 'process my inbox', 'what's new in my email', 'handle my email', 'email triage'). Requires the inbox-setup skill to have been run first.\"\nlicense: MIT\nmetadata:\n  source_spec: \"megaprompts\u002F07-inbox-triage-megaprompt.md\"\n  build_pattern: \"Path B (direct conversion)\"\n  paired_with: \"inbox-setup (consumes the 7-file KB it produces)\"\n  version: 1.0.0\n---\n\n# Inbox-Triage — Recurring Email Triage\n\n> **Paired with `inbox-setup`.** This skill consumes the 7-file knowledge base that `inbox-setup` writes at `${WORKSPACE}\u002FEmail\u002F`. The file contracts MUST match exactly. See [`references\u002Fkb_file_contract.md`](references\u002Fkb_file_contract.md) — this is the mirror of the setup-side contract, viewed from the read side.\n\nRun on a recurring schedule (1–3x daily) or on demand. Classify recent emails, research new senders, generate decision recommendations, draft replies (**NEVER SEND**), deliver a clean report, and update the knowledge base with what was learned this run.\n\n## Invocation Triggers\n\n- \"triage my inbox\"\n- \"inbox triage\"\n- \"check my email\"\n- \"run email triage\"\n- \"process my inbox\"\n- \"what's new in my email\"\n- \"handle my email\"\n- \"email triage\"\n\n## Prerequisites\n\nRequired reads at start (fail-fast if missing):\n\n**Core (required):**\n- `${WORKSPACE}\u002FEmail\u002Femail-taxonomy.md` — classification + report preferences\n- `${WORKSPACE}\u002FEmail\u002Femail-patterns.md` — voice, persona, templates, hard rules\n\n**Optional core (read if exists):**\n- `${WORKSPACE}\u002FEmail\u002Fevaluation-framework.md`\n- `${WORKSPACE}\u002FEmail\u002Frate-card.md`\n\n**Evolving (read AND update every run):**\n- `${WORKSPACE}\u002FEmail\u002Fblocklist.md`\n- `${WORKSPACE}\u002FEmail\u002Ftracker.md`\n\n**Output:**\n- `${WORKSPACE}\u002FEmail\u002Ftriage-log\u002F\u003CYYYY-MM-DD>-\u003Crun-label>.md` — per-run log\n\nIf any core required file is missing → **halt**, direct user to run `inbox-setup` first. Use `scripts\u002Fkb_reader.py` to perform the read + validation.\n\n## DRAFTS ONLY — Never Send\n\n> **This skill creates drafts. It NEVER sends.**\n\nThis is the safety property that makes the skill safe to run automatically. Stated multiple times in this skill body. Non-negotiable.\n\nThe `scripts\u002Fdraft_safety_validator.py` enforces it post-run. Any send-shaped tool call in the action log fails validation. See [`references\u002Fdrafts_only_safety.md`](references\u002Fdrafts_only_safety.md) for the full discipline canon.\n\n## Step 0: Grill-Me Intake (Light — 0–2 Optional Override Questions)\n\nInbox-triage is **light-intake by design** — it runs on a recurring cadence with preferences pre-baked into the knowledge base from `inbox-setup`. The grill-me discipline here is asking ONLY the override questions that matter THIS run.\n\n### Q1 (optional, asked only when on-demand run is outside normal cadence)\n\n> **Override the default 9-hour search window? Pick: yes (specify hours) \u002F no (use default).**\n>\n> *Why I'm asking:* If you're running on-demand outside your normal 2x\u002Fday cadence, you may want a wider window (24h after a long break) or narrower (2h for a quick check).\n\nSkip if cadence is normal.\n\n### Q2 (optional, asked only when user invokes with category-skip intent)\n\n> **Skip any categories this run? E.g., \"skip newsletters\", \"skip financial\".**\n>\n> *Why I'm asking:* Sometimes you just want to scan opportunities or just want to clear active threads. Category skip narrows the run scope.\n\nSkip if user gave no category-skip signal.\n\n**Stop condition:** Max 2 questions. Default invocations skip both questions and run with KB-default preferences. The skill is optimized for fast recurring execution; intake is the exception, not the norm.\n\n## Step 1: Determine Search Window\n\nCompute via current date math. Default lookback: **9 hours** (works for 2x\u002Fday cadence with slight overlap so emails between runs aren't missed).\n\nUse `scripts\u002Fsearch_window_calculator.py --cadence \u003CCADENCE> --now \u003CISO>`:\n\n```\nnow = current_datetime\nwindow_start = now - 9_hours   (default for 2x-daily)\nrun_label = \"Morning\" if now.hour \u003C 12 else \"Afternoon\" if now.hour \u003C 17 else \"Evening\"\n```\n\nCadence-to-default-window mapping (override via Q1):\n\n| Cadence (from email-taxonomy.md S1.Q5) | Default window |\n|---|---|\n| once daily | 26h |\n| 2x daily | 9h |\n| 3x daily | 6h |\n| on-demand only | 24h (asks Q1) |\n\n## Step 2: Email Search\n\nTwo queries (provider-agnostic adapter pattern):\n\n- **Primary:** Inbox + sent after `window_start`\n- **Secondary:** Starred unread (catch flagged items missed in primary)\n\nCollect for each email: sender, subject, date, snippet, thread ID, labels.\n\nProvider adapter mapping:\n\n| Provider | Tool |\n|---|---|\n| Gmail | Gmail MCP |\n| Outlook \u002F Microsoft 365 | Outlook MCP |\n| IMAP (Fastmail, ProtonMail, etc.) | IMAP MCP if available; halt otherwise |\n| (no email tool available) | Halt with clear message: \"No email tool registered for this session.\" |\n\n## Step 3: Classification\n\nApply the taxonomy from `email-taxonomy.md`. For **lowest-priority** category (newsletters \u002F automation \u002F spam): skip thread reads entirely — context cost not worth it. For everything else: read full thread.\n\n## Step 4: Sender Research\n\nFor senders not in tracker \u002F blocklist \u002F prior logs:\n\n1. Check `blocklist.md` → if matched, auto-skip\n2. Check `tracker.md` → if known thread, note existing context\n3. For opportunity senders (per evaluation framework): web search for company legitimacy, social presence, intermediary status\n\n**Skip research entirely** for: known senders (in tracker), internal email, automated notifications, obvious low-priority.\n\n## Step 5: Recommendations\n\nFor decision-required emails, apply the framework from `evaluation-framework.md`. Categorize:\n\n| Category | When | Output |\n|---|---|---|\n| **TAKE IT** | Meets criteria | Recommend engaging; draft reply (Step 6) |\n| **WORTH CONSIDERING** | Has potential, needs user judgment | Surface key context; draft for user to edit |\n| **PASS** | Doesn't meet criteria | Brief \"why\" (1–3 sentences); draft polite decline |\n| **FLAG FOR REVIEW** | Unusual; needs direct user decision | Surface fully; NO draft (user decides response shape) |\n\nEach: brief \"why\", relevant context, pricing\u002Ftimeline comparison if applicable.\n\n**Skip Step 5 entirely if no `evaluation-framework.md` exists.**\n\nSee [`references\u002Ftriage_decision_framework.md`](references\u002Ftriage_decision_framework.md) for the framework canon.\n\n## Step 6: Drafts\n\nFor every reasonable reply candidate, create a draft using `email-patterns.md` voice rules.\n\n**Draft for:** opportunity responses (TAKE IT \u002F WORTH \u002F PASS), active conversations needing reply, action items, important personal emails.\n\n**Do NOT draft for:**\n- Clearly no-response emails (newsletters, automation, FYI)\n- Threads where user already replied\n- Blocked senders (unless new info changes the calculus)\n\n**Mechanics:**\n\n- Draft only in the existing thread when possible (preserves context)\n- Set `to`, `subject` (`Re: [original]`)\n- **NEVER call any send operation. Only create drafts.**\n\nThe draft body MUST honor:\n- Voice register from `email-patterns.md`\n- Forbidden tokens (S3.Q2 pet peeves)\n- Sign-off patterns\n- Persona context\n- Hard rules (S3.Q6 — non-negotiable)\n- Reply length per `email-patterns.md`\n\nIf `evaluation-framework.md` exists, draft tone matches recommendation:\n- TAKE IT → engaged + concrete next step\n- WORTH → curious + 1-2 clarifying questions\n- PASS → polite decline + brief reason (no hedging promises)\n- FLAG → NO draft\n\n## Step 7: Report Delivery\n\nHonor user's preference from `email-taxonomy.md` \"Report Preferences\" section. Default: email draft to self with HTML.\n\n**Subject:** `Inbox Triage — [Day], [Month Date] ([Run Label])`\n\n**Sections (in order):**\n\n1. **Overview** — 2–3 sentences. What happened? Anything urgent?\n2. **Stats** — Counts: processed, drafts created, action needed, skipped.\n3. **Action Needed** — Overdue items, decisions, drafts to review, deadlines.\n4. **Quick Reference** — One line per email, alphabetical by sender. `**Sender** — one-sentence summary + recommendation`.\n5. **Detailed Cards** — Opportunities, active threads, flags. Each: sender \u002F subject \u002F category, recommendation + reasoning, key context. **NO draft text previews** (drafts are already in email client for user to read there).\n6. **Footer** — Generation timestamp + KB update summary.\n\n**Formatting (if HTML):**\n\n- **Inline CSS only** (Gmail strips `\u003Cstyle>`)\n- Color-coded by recommendation:\n  - green → TAKE IT\n  - amber → WORTH CONSIDERING\n  - red → PASS\n  - purple → FLAG FOR REVIEW\n  - blue → active conversation\n\n## Step 8: Knowledge Base Update\n\n**`blocklist.md`** (append new):\n\n- New declined senders + reason + date\n- New decline patterns from observed behavior (e.g., \"all emails containing 'looking for backend engineers' from gmail addresses → cold recruiter pattern\")\n- Remove entries if user has overridden them (user replied to a \"blocked\" sender → unblock)\n\n**`tracker.md`** (append + update):\n\n- New follow-ups for emails needing future action\n- Update existing follow-ups (deadline changed, status changed)\n- Mark resolved items complete\n- Flag overdue items\n- Remove resolved items older than 30 days\n- Add entry to update log\n\n**Learning patterns to observe over runs:**\n\n- Drafts sent as-is vs. edited vs. deleted → tone calibration signal\n- PASS recommendations user overrides → framework adjustment signal\n- Engaged vs. ignored emails → taxonomy refinement signal\n- New decline patterns → blocklist additions\n\nAfter 5+ runs, suggest KB improvements to user (e.g., \"You always decline emails from X — add as auto-skip?\").\n\n## Step 9: Internal Log\n\nSave to `${WORKSPACE}\u002FEmail\u002Ftriage-log\u002F[YYYY-MM-DD]-[run-label].md`:\n\n- Emails processed with classifications\n- Recommendations made\n- Drafts created (with IDs \u002F thread refs)\n- KB updates made\n- Follow-ups added \u002F resolved\n- Notable observations (patterns surfaced, edge cases handled)\n\nThe log is the audit trail for `scripts\u002Fdraft_safety_validator.py` to scan for send operations post-run.\n\n## Step 10: Empty Inbox Handling\n\nEven with zero new emails:\n\n1. Check `tracker.md` for items due today or overdue\n2. Generate minimal report: \"No new actionable emails since last run\"\n3. Flag any overdue items\n4. Escalate per tracker rules\n\nSkip Steps 3–6 entirely on empty inbox.\n\n## Critical Rules (Stated Multiple Times)\n\n1. **DRAFTS ONLY — NEVER SEND.** Non-negotiable. Stated again here.\n2. **Privacy.** No passwords \u002F credentials in KB. Reference threads by ID for sensitive content.\n3. **Accuracy over speed.** When unsure, flag for review. A wrong auto-draft is worse than no draft.\n4. **Respect the KB.** Documented preferences are source of truth. Don't override with judgment.\n5. **Transparency.** Note every KB change in the triage log.\n6. **First runs need oversight.** Document this expectation for the user.\n\n## Error Handling\n\n| Situation | Behavior |\n|---|---|\n| KB files missing | Halt; direct user to run `inbox-setup` |\n| Email tool unavailable | Halt with clear message about required tool |\n| Web search unavailable for sender research | Skip research step; note senders not researched |\n| Draft creation fails | Skip that draft; note in log; report continues |\n| Report delivery fails | Save report to file as fallback; notify user |\n| User has 100+ new emails | Stay within reasonable limits; flag volume; offer to focus on priority categories only |\n| Sender appears in both blocklist and tracker | Tracker wins (active conversation); note inconsistency in log |\n\n## Portability\n\n- **Claude Code CLI:** Native — uses Gmail \u002F Outlook MCP, file tools for KB, web search for research.\n- **Claude.ai web:** Works when email MCP connector is connected (Gmail MCP available). Skill must check tool availability before assuming. If no email tool: halt with clear message.\n\n## Tooling\n\n| Script | Role |\n|---|---|\n| `scripts\u002Fkb_reader.py` | Reads + validates the 7-file KB. Returns parsed structure. Halts with explicit error if required files missing. |\n| `scripts\u002Fsearch_window_calculator.py` | Computes `window_start` from cadence + current time. Returns `run_label`. Honors Q1 override. |\n| `scripts\u002Fdraft_safety_validator.py` | Post-run scan of the action log for any send-shaped tool call. FAILs if detected. The deterministic enforcement of the NEVER-SEND rule. |\n\n## References\n\n- [`references\u002Fkb_file_contract.md`](references\u002Fkb_file_contract.md) — canonical 7-file contract (read perspective; mirrors `..\u002Finbox-setup\u002Freferences\u002Fkb_file_contract.md`)\n- [`references\u002Ftriage_decision_framework.md`](references\u002Ftriage_decision_framework.md) — TAKE IT \u002F WORTH \u002F PASS \u002F FLAG taxonomy\n- [`references\u002Fdrafts_only_safety.md`](references\u002Fdrafts_only_safety.md) — the NEVER-SEND discipline canon\n\n## Anti-Patterns To Reject\n\n- **Sending emails** (drafts only — non-negotiable)\n- Operating without knowledge base files\n- Storing passwords \u002F credentials in KB\n- Skipping the learning loop (KB updates) at end of run\n- Overriding user's documented preferences with own judgment\n- Reading lowest-priority threads (waste of context)\n- Including draft text previews in report (drafts are already in email client)\n- Provider lock-in without adapter pattern\n- Silently failing on missing tools\n\n---\n\n**Version:** 1.0.0\n**Source spec:** `megaprompts\u002F07-inbox-triage-megaprompt.md` (maintainer-local draft spec — gitignored, not present in the public repository)\n**Build pattern:** Path B (direct conversion). Paired with `inbox-setup`.\n","# Inbox-Triage — Recurring Email Triage\n\n> **Paired with `inbox-setup`.** This skill consumes the 7-file knowledge base that `inbox-setup` writes at `${WORKSPACE}\u002FEmail\u002F`. The file contracts MUST match exactly. See [`references\u002Fkb_file_contract.md`](references\u002Fkb_file_contract.md) — this is the mirror of the setup-side contract, viewed from the read side.\n\nRun on a recurring schedule (1–3x daily) or on demand. Classify recent emails, research new senders, generate decision recommendations, draft replies (**NEVER SEND**), deliver a clean report, and update the knowledge base with what was learned this run.\n\n## Invocation Triggers\n\n- \"triage my inbox\"\n- \"inbox triage\"\n- \"check my email\"\n- \"run email triage\"\n- \"process my inbox\"\n- \"what's new in my email\"\n- \"handle my email\"\n- \"email triage\"\n\n## Prerequisites\n\nRequired reads at start (fail-fast if missing):\n\n**Core (required):**\n- `${WORKSPACE}\u002FEmail\u002Femail-taxonomy.md` — classification + report preferences\n- `${WORKSPACE}\u002FEmail\u002Femail-patterns.md` — voice, persona, templates, hard rules\n\n**Optional core (read if exists):**\n- `${WORKSPACE}\u002FEmail\u002Fevaluation-framework.md`\n- `${WORKSPACE}\u002FEmail\u002Frate-card.md`\n\n**Evolving (read AND update every run):**\n- `${WORKSPACE}\u002FEmail\u002Fblocklist.md`\n- `${WORKSPACE}\u002FEmail\u002Ftracker.md`\n\n**Output:**\n- `${WORKSPACE}\u002FEmail\u002Ftriage-log\u002F\u003CYYYY-MM-DD>-\u003Crun-label>.md` — per-run log\n\nIf any core required file is missing → **halt**, direct user to run `inbox-setup` first. Use `scripts\u002Fkb_reader.py` to perform the read + validation.\n\n## DRAFTS ONLY — Never Send\n\n> **This skill creates drafts. It NEVER sends.**\n\nThis is the safety property that makes the skill safe to run automatically. Stated multiple times in this skill body. Non-negotiable.\n\nThe `scripts\u002Fdraft_safety_validator.py` enforces it post-run. Any send-shaped tool call in the action log fails validation. See [`references\u002Fdrafts_only_safety.md`](references\u002Fdrafts_only_safety.md) for the full discipline canon.\n\n## Step 0: Grill-Me Intake (Light — 0–2 Optional Override Questions)\n\nInbox-triage is **light-intake by design** — it runs on a recurring cadence with preferences pre-baked into the knowledge base from `inbox-setup`. The grill-me discipline here is asking ONLY the override questions that matter THIS run.\n\n### Q1 (optional, asked only when on-demand run is outside normal cadence)\n\n> **Override the default 9-hour search window? Pick: yes (specify hours) \u002F no (use default).**\n>\n> *Why I'm asking:* If you're running on-demand outside your normal 2x\u002Fday cadence, you may want a wider window (24h after a long break) or narrower (2h for a quick check).\n\nSkip if cadence is normal.\n\n### Q2 (optional, asked only when user invokes with category-skip intent)\n\n> **Skip any categories this run? E.g., \"skip newsletters\", \"skip financial\".**\n>\n> *Why I'm asking:* Sometimes you just want to scan opportunities or just want to clear active threads. Category skip narrows the run scope.\n\nSkip if user gave no category-skip signal.\n\n**Stop condition:** Max 2 questions. Default invocations skip both questions and run with KB-default preferences. The skill is optimized for fast recurring execution; intake is the exception, not the norm.\n\n## Step 1: Determine Search Window\n\nCompute via current date math. Default lookback: **9 hours** (works for 2x\u002Fday cadence with slight overlap so emails between runs aren't missed).\n\nUse `scripts\u002Fsearch_window_calculator.py --cadence \u003CCADENCE> --now \u003CISO>`:\n\n```\nnow = current_datetime\nwindow_start = now - 9_hours   (default for 2x-daily)\nrun_label = \"Morning\" if now.hour \u003C 12 else \"Afternoon\" if now.hour \u003C 17 else \"Evening\"\n```\n\nCadence-to-default-window mapping (override via Q1):\n\n| Cadence (from email-taxonomy.md S1.Q5) | Default window |\n|---|---|\n| once daily | 26h |\n| 2x daily | 9h |\n| 3x daily | 6h |\n| on-demand only | 24h (asks Q1) |\n\n## Step 2: Email Search\n\nTwo queries (provider-agnostic adapter pattern):\n\n- **Primary:** Inbox + sent after `window_start`\n- **Secondary:** Starred unread (catch flagged items missed in primary)\n\nCollect for each email: sender, subject, date, snippet, thread ID, labels.\n\nProvider adapter mapping:\n\n| Provider | Tool |\n|---|---|\n| Gmail | Gmail MCP |\n| Outlook \u002F Microsoft 365 | Outlook MCP |\n| IMAP (Fastmail, ProtonMail, etc.) | IMAP MCP if available; halt otherwise |\n| (no email tool available) | Halt with clear message: \"No email tool registered for this session.\" |\n\n## Step 3: Classification\n\nApply the taxonomy from `email-taxonomy.md`. For **lowest-priority** category (newsletters \u002F automation \u002F spam): skip thread reads entirely — context cost not worth it. For everything else: read full thread.\n\n## Step 4: Sender Research\n\nFor senders not in tracker \u002F blocklist \u002F prior logs:\n\n1. Check `blocklist.md` → if matched, auto-skip\n2. Check `tracker.md` → if known thread, note existing context\n3. For opportunity senders (per evaluation framework): web search for company legitimacy, social presence, intermediary status\n\n**Skip research entirely** for: known senders (in tracker), internal email, automated notifications, obvious low-priority.\n\n## Step 5: Recommendations\n\nFor decision-required emails, apply the framework from `evaluation-framework.md`. Categorize:\n\n| Category | When | Output |\n|---|---|---|\n| **TAKE IT** | Meets criteria | Recommend engaging; draft reply (Step 6) |\n| **WORTH CONSIDERING** | Has potential, needs user judgment | Surface key context; draft for user to edit |\n| **PASS** | Doesn't meet criteria | Brief \"why\" (1–3 sentences); draft polite decline |\n| **FLAG FOR REVIEW** | Unusual; needs direct user decision | Surface fully; NO draft (user decides response shape) |\n\nEach: brief \"why\", relevant context, pricing\u002Ftimeline comparison if applicable.\n\n**Skip Step 5 entirely if no `evaluation-framework.md` exists.**\n\nSee [`references\u002Ftriage_decision_framework.md`](references\u002Ftriage_decision_framework.md) for the framework canon.\n\n## Step 6: Drafts\n\nFor every reasonable reply candidate, create a draft using `email-patterns.md` voice rules.\n\n**Draft for:** opportunity responses (TAKE IT \u002F WORTH \u002F PASS), active conversations needing reply, action items, important personal emails.\n\n**Do NOT draft for:**\n- Clearly no-response emails (newsletters, automation, FYI)\n- Threads where user already replied\n- Blocked senders (unless new info changes the calculus)\n\n**Mechanics:**\n\n- Draft only in the existing thread when possible (preserves context)\n- Set `to`, `subject` (`Re: [original]`)\n- **NEVER call any send operation. Only create drafts.**\n\nThe draft body MUST honor:\n- Voice register from `email-patterns.md`\n- Forbidden tokens (S3.Q2 pet peeves)\n- Sign-off patterns\n- Persona context\n- Hard rules (S3.Q6 — non-negotiable)\n- Reply length per `email-patterns.md`\n\nIf `evaluation-framework.md` exists, draft tone matches recommendation:\n- TAKE IT → engaged + concrete next step\n- WORTH → curious + 1-2 clarifying questions\n- PASS → polite decline + brief reason (no hedging promises)\n- FLAG → NO draft\n\n## Step 7: Report Delivery\n\nHonor user's preference from `email-taxonomy.md` \"Report Preferences\" section. Default: email draft to self with HTML.\n\n**Subject:** `Inbox Triage — [Day], [Month Date] ([Run Label])`\n\n**Sections (in order):**\n\n1. **Overview** — 2–3 sentences. What happened? Anything urgent?\n2. **Stats** — Counts: processed, drafts created, action needed, skipped.\n3. **Action Needed** — Overdue items, decisions, drafts to review, deadlines.\n4. **Quick Reference** — One line per email, alphabetical by sender. `**Sender** — one-sentence summary + recommendation`.\n5. **Detailed Cards** — Opportunities, active threads, flags. Each: sender \u002F subject \u002F category, recommendation + reasoning, key context. **NO draft text previews** (drafts are already in email client for user to read there).\n6. **Footer** — Generation timestamp + KB update summary.\n\n**Formatting (if HTML):**\n\n- **Inline CSS only** (Gmail strips `\u003Cstyle>`)\n- Color-coded by recommendation:\n  - green → TAKE IT\n  - amber → WORTH CONSIDERING\n  - red → PASS\n  - purple → FLAG FOR REVIEW\n  - blue → active conversation\n\n## Step 8: Knowledge Base Update\n\n**`blocklist.md`** (append new):\n\n- New declined senders + reason + date\n- New decline patterns from observed behavior (e.g., \"all emails containing 'looking for backend engineers' from gmail addresses → cold recruiter pattern\")\n- Remove entries if user has overridden them (user replied to a \"blocked\" sender → unblock)\n\n**`tracker.md`** (append + update):\n\n- New follow-ups for emails needing future action\n- Update existing follow-ups (deadline changed, status changed)\n- Mark resolved items complete\n- Flag overdue items\n- Remove resolved items older than 30 days\n- Add entry to update log\n\n**Learning patterns to observe over runs:**\n\n- Drafts sent as-is vs. edited vs. deleted → tone calibration signal\n- PASS recommendations user overrides → framework adjustment signal\n- Engaged vs. ignored emails → taxonomy refinement signal\n- New decline patterns → blocklist additions\n\nAfter 5+ runs, suggest KB improvements to user (e.g., \"You always decline emails from X — add as auto-skip?\").\n\n## Step 9: Internal Log\n\nSave to `${WORKSPACE}\u002FEmail\u002Ftriage-log\u002F[YYYY-MM-DD]-[run-label].md`:\n\n- Emails processed with classifications\n- Recommendations made\n- Drafts created (with IDs \u002F thread refs)\n- KB updates made\n- Follow-ups added \u002F resolved\n- Notable observations (patterns surfaced, edge cases handled)\n\nThe log is the audit trail for `scripts\u002Fdraft_safety_validator.py` to scan for send operations post-run.\n\n## Step 10: Empty Inbox Handling\n\nEven with zero new emails:\n\n1. Check `tracker.md` for items due today or overdue\n2. Generate minimal report: \"No new actionable emails since last run\"\n3. Flag any overdue items\n4. Escalate per tracker rules\n\nSkip Steps 3–6 entirely on empty inbox.\n\n## Critical Rules (Stated Multiple Times)\n\n1. **DRAFTS ONLY — NEVER SEND.** Non-negotiable. Stated again here.\n2. **Privacy.** No passwords \u002F credentials in KB. Reference threads by ID for sensitive content.\n3. **Accuracy over speed.** When unsure, flag for review. A wrong auto-draft is worse than no draft.\n4. **Respect the KB.** Documented preferences are source of truth. Don't override with judgment.\n5. **Transparency.** Note every KB change in the triage log.\n6. **First runs need oversight.** Document this expectation for the user.\n\n## Error Handling\n\n| Situation | Behavior |\n|---|---|\n| KB files missing | Halt; direct user to run `inbox-setup` |\n| Email tool unavailable | Halt with clear message about required tool |\n| Web search unavailable for sender research | Skip research step; note senders not researched |\n| Draft creation fails | Skip that draft; note in log; report continues |\n| Report delivery fails | Save report to file as fallback; notify user |\n| User has 100+ new emails | Stay within reasonable limits; flag volume; offer to focus on priority categories only |\n| Sender appears in both blocklist and tracker | Tracker wins (active conversation); note inconsistency in log |\n\n## Portability\n\n- **Claude Code CLI:** Native — uses Gmail \u002F Outlook MCP, file tools for KB, web search for research.\n- **Claude.ai web:** Works when email MCP connector is connected (Gmail MCP available). Skill must check tool availability before assuming. If no email tool: halt with clear message.\n\n## Tooling\n\n| Script | Role |\n|---|---|\n| `scripts\u002Fkb_reader.py` | Reads + validates the 7-file KB. Returns parsed structure. Halts with explicit error if required files missing. |\n| `scripts\u002Fsearch_window_calculator.py` | Computes `window_start` from cadence + current time. Returns `run_label`. Honors Q1 override. |\n| `scripts\u002Fdraft_safety_validator.py` | Post-run scan of the action log for any send-shaped tool call. FAILs if detected. The deterministic enforcement of the NEVER-SEND rule. |\n\n## References\n\n- [`references\u002Fkb_file_contract.md`](references\u002Fkb_file_contract.md) — canonical 7-file contract (read perspective; mirrors `..\u002Finbox-setup\u002Freferences\u002Fkb_file_contract.md`)\n- [`references\u002Ftriage_decision_framework.md`](references\u002Ftriage_decision_framework.md) — TAKE IT \u002F WORTH \u002F PASS \u002F FLAG taxonomy\n- [`references\u002Fdrafts_only_safety.md`](references\u002Fdrafts_only_safety.md) — the NEVER-SEND discipline canon\n\n## Anti-Patterns To Reject\n\n- **Sending emails** (drafts only — non-negotiable)\n- Operating without knowledge base files\n- Storing passwords \u002F credentials in KB\n- Skipping the learning loop (KB updates) at end of run\n- Overriding user's documented preferences with own judgment\n- Reading lowest-priority threads (waste of context)\n- Including draft text previews in report (drafts are already in email client)\n- Provider lock-in without adapter pattern\n- Silently failing on missing tools\n\n---\n\n**Version:** 1.0.0\n**Source spec:** `megaprompts\u002F07-inbox-triage-megaprompt.md` (maintainer-local draft spec — gitignored, not present in the public repository)\n**Build pattern:** Path B (direct conversion). Paired with `inbox-setup`.\n",{"name":5,"license":14,"metadata":51,"description":7},{"version":52,"paired_with":53,"source_spec":54,"build_pattern":55},"1.0.0","inbox-setup (consumes the 7-file KB it produces)","megaprompts\u002F07-inbox-triage-megaprompt.md","Path B (direct conversion)","main","510dd2917e051cc953dc55f56fd6ef442aa01b38","claude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-triage","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi","https:\u002F\u002Fgithub.com\u002Fmne20114-hash","2026-10-28 07:50:31",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add mne20114-hash\u002Fgest35bi --skill inbox-triage",{"tool":68,"command":69},"bunx","bunx skills add mne20114-hash\u002Fgest35bi --skill inbox-triage",{"tool":71,"command":72},"pnpm","pnpm dlx skills add mne20114-hash\u002Fgest35bi --skill inbox-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-triage\u002FSKILL.md",true,[76,82,86,90,96,100],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fdrafts_only_safety.md","REFERENCE","参考文档",7408,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-triage\u002Freferences\u002Fdrafts_only_safety.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fkb_file_contract.md",6164,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-triage\u002Freferences\u002Fkb_file_contract.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Ftriage_decision_framework.md",7450,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-triage\u002Freferences\u002Ftriage_decision_framework.md",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fdraft_safety_validator.py","SCRIPT","脚本",7046,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-triage\u002Fscripts\u002Fdraft_safety_validator.py",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fkb_reader.py",11871,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-triage\u002Fscripts\u002Fkb_reader.py",{"path":101,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fsearch_window_calculator.py",5217,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fproductivity\u002Femail\u002Fskills\u002Finbox-triage\u002Fscripts\u002Fsearch_window_calculator.py",[105,139,159,182,206,226],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":122,"publishedAt":46},"01M6C27N3H0F9RGG2KASPASH04","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[111,114,117],{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[107,123,124,125,43,126,127,128,129,130,131,36,132,133,134,135,136,137,29,138],"docx","pr","create","search","audit","integrity","checkpoint","learning","js","direct","Rules","find","consensus","list","extract","outcomes",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":147,"publishedAt":46},"01M6C27DMGZ4D6ERNHSVA8H8RJ","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[145,146],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},[141,148,149,124,150,43,127,151,152,128,153,154,155,156,132,133,157,134,158,29],"research","web","sentiment analysis","sentiment","Citations","analysis","discovery","open","tool","twitter","user",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":170,"publishedAt":46},"01M6C279M59X635VPD6Y9R616J","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[165,166,167],{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":168,"categoryName":169,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000037","律师与法务",[161,123,124,171,172,173,43,126,127,153,174,175,176,133,177,178,179,180,29,181],"competitive landscape","routing","product","commits","Word","text","acquisition","decisions","strategy","coverage","advice",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":192,"publishedAt":46},"01M6C275RZWNRB3CCB14QQM7ES","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[188,191],{"categoryNo":189,"categoryName":190,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},[184,193,194,148,195,196,197,198,199,200,201,202,155,176,132,34,203,204,205,29],"google","browser automation","automation","generate","browser","fast","SET","doc","Video","Audio","ask","environment","overview",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":216,"publishedAt":46},"01M6C2717B0QDJ3Y4PJP77BMW5","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[212,213,214,215],{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[208,123,217,218,219,124,43,126,220,221,222,129,223,175,224,133,135,225,180,29],"MCP","writing","review","lane","keyless","literature review","plan","researcher","question",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":236,"publishedAt":46},"01M6C26X5G3WDVWQ40Y16ZS19F","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[232,233,234,235],{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[228,123,148,124,237,43,126,127,238,239,128,153,175,133,134,135,179,204,29,240],"help","data","Budget","innovation"]