inbox
Email triage system that handles both one-time setup and recurring triage in a single skill. Auto-detects state: if no knowledge base exists at ${WORKSPACE}/Email/, runs an 8-section onboarding interview (grill-me discipline, one question at a time) to build a 7-file personalized KB, then offers to run triage immediately. If the KB already exists, skips setup and goes straight to triage — searches recent emails, classifies them via the user's taxonomy, researches new senders, generates TAKE IT/WORTH/PASS/FLAG recommendations, drafts replies (NEVER sends), delivers a report, and updates the KB.
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill inbox --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Inbox — Email Triage System Self-contained email triage skill. Handles setup and recurring triage in a single command. Detects its own state and routes accordingly — no need to remember which mode to run. ## State Detection (Always First) Before anything else, check for the KB: | State | Route | |---|---| | Argument is `update` | → **Update Mode** | | `${WORKSPACE}/Email/email-taxonomy.md` does NOT exist | → **Setup Mode** | | `${WORKSPACE}/Email/email-taxonomy.md` exists | → **Triage Mode** | **Edge cases:** - User says "set up my inbox" but KB exists → acknowledge, ask: "run triage / update preferences / both?" - User says "triage my inbox" but no KB → "No knowledge base found. Running setup first, then triage immediately after." → Setup → Triage - Partial KB (some files missing) → list which files are missing, ask: "run full setup / fill in only the missing sections?" --- ## SETUP MODE — Build the Knowledge Base Runs when no KB exists. ### Conduct Discipline **Do NOT generate all files at once.** Walk through the 8 sections one at a time. Each section commits its file(s) before moving on. Partial completion (user drops off mid-interview) still produces a usable partial KB. - *
- State Detection (Always First)
- SETUP MODE — Build the Knowledge Base
- Conduct Discipline
- Knowledge Base — 7 Files to Produce
- Stop Condition
- Section 1: The Big Picture
- Section 2: Email Categories
- Section 3: Reply Style & Voice
- Section 4: Evaluation Framework (Conditional)
- Section 5: Blocklist & Patterns
- Section 6: Current State
- Section 7: Report Preferences
- Section 8: Confirmation & Handoff
- Privacy Boundary
What does the inbox skill do?
Email triage system that handles both one-time setup and recurring triage in a single skill. Auto-detects state: if no knowledge base exists at ${WORKSPACE}/Email/, runs an 8-section onboarding interview (grill-me discipline, one question at a time) to build a 7-file personalized KB, then offers to run triage immediately. If the KB already exists, skips setup and goes straight to triage — searches recent emails, classifies them via the user's taxonomy, researches new senders, generates TAKE IT/WORTH/PASS/FLAG recommendations, drafts replies (NEVER sends), delivers a report, and updates the KB.
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill inbox --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.