inbox-triage

Classifies raw inbox captures and routes them to tasks, calendar, follow-ups, or archives.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/hivgb1-ai/do-better-workspace-v2 --skill inbox-triage-hivgb1-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inbox-triage
Source: https://github.com/hivgb1-ai/do-better-workspace-v2/tree/main/.claude/skills/inbox-triage
Command: npx skills add https://github.com/hivgb1-ai/do-better-workspace-v2 --skill inbox-triage-hivgb1-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Collected messages, call transcripts, and notifications pile up in a raw inbox folder with no structure, forcing you to manually read and sort every item. This Skill reads each unprocessed capture, judges what kind of item it is, and routes it to the right destination so nothing gets lost or double-handled. ## Core Features & Use Cases - Cascading classification: Applies cheap frontmatter signal gates first (OTP codes, payment alerts, persistent noise lists), then deeper body-content judgment into five fixed types (task, calendar, follow-up, info, noise) plus declared business categories, each with an explicit confidence score. - Delegated routing with execution tiers: Reversible actions (todo registration, info archiving, noise marking) execute immediately with after-the-fact reporting, while outbound actions (sending replies, confirming calendar events, money matters) always require explicit human confirmation. - Call transcript handling: Two-tier gate separates single-topic calls (lightweight inline fact-card extraction with STT misrecognition correction) from multi-topic meetings (handed off to a transcript organizer). - Use Case: After collectors drop KakaoTalk messages and call recordings into 00-inbox/raw/, say "인박스 분류해줘" and receive a table showing each item's type, confidence, destination, and what was already done versus what needs your approval. ## Quick Start Ask the assistant to triage the raw inbox by saying "인박스 분류해줘" to classify all unprocessed captures and route them to their destinations.

Frequently Asked Questions about inbox-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically sort an inbox of collected messages?

Run the triage command on the raw inbox folder and each unprocessed file is classified by cascading gates: surface signals first, then body content. Items become tasks, calendar events, follow-ups, info, or noise, with reversible actions executed immediately and outbound actions held for your approval.

How does confidence-based message classification work?

Each item receives a confidence score from 0.0 to 1.0 based on signal strength: machine-readable frontmatter signals score 0.9 or higher, clear single body signals score 0.7 to 0.8, and ambiguous items fall below 0.7. Anything under 0.7 is quarantined as unclassified until a human decides.

Can the triage handle phone call transcripts with STT errors?

Yes, single-topic calls get lightweight inline processing that extracts a six-field fact card and corrects STT misrecognitions by grepping declared correction sources for company and person names. Multi-topic meetings are handed off to a dedicated transcript organizer instead.

Does the classifier delete noise messages like OTP codes?

No, noise items are never deleted. They are marked with a noise_type tag and preserved, so filtered payment alerts or vendor notifications remain greppable as a domain dataset later. Only OTP and verification codes are blocked at the collection stage.

What prevents the same inbox item from being processed twice?

Processed files receive frontmatter markers like routed_to or triage_held, and the scan step excludes any file carrying these markers even if processed is still false. Duplicate messages arriving through two streams are marked as dup-of with the original's unique identifier.