taskflow-inbox-triage

Classify inbox messages by intent and route them through a managed TaskFlow lifecycle.

Updated May 8, 2026
One-click install
npx skills add https://github.com/freire19/Mythos --skill taskflow-inbox-triage-freire19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskflow-inbox-triage
Source: https://github.com/freire19/Mythos/tree/main/skills/taskflow-inbox-triage
Command: npx skills add https://github.com/freire19/Mythos --skill taskflow-inbox-triage-freire19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of inbox overload by automatically routing incoming messages to the right handling path based on intent, while managing when work should wait for external replies versus roll up into later summaries.

Core Features & Use Cases

  • Intent-based routing: Classifies inbox items and sends business messages into a waiting state for an outside answer, while immediately notifying the owner for personal items.
  • Managed multi-step flow: Uses a structured flow lifecycle (classify → wait → resume → route → finish) so each inbox batch is handled deterministically.
  • Persisted state & wait contracts: Stores routing state in stateJson and expresses blocking conditions through a waitJson object (e.g., Slack thread reply).
  • End-of-day consolidation: Keeps non-triageable or general items in an end-of-day summary bucket.

Quick Start

Use taskflow-inbox-triage to triage a batch of inbox messages by classifying intent, notifying immediately when appropriate, and waiting for Slack replies when needed before finishing the batch.

Frequently Asked Questions about taskflow-inbox-triage

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

FAQPage Schema
How do I automate inbox triage and route messages based on intent?

Inbox triage automation classifies incoming messages by intent and routes each item into the correct handling path, such as immediate notifications or waiting states. This structured flow manages batches deterministically from classification to finish.

How does intent-aware routing handle messages waiting for Slack replies?

Intent-aware routing uses a typed waitJson contract to express blocking conditions like a Slack thread reply. Business messages enter a waiting state and persist their routing state in stateJson until the external answer is received.

What is the best way to consolidate non-triageable inbox items for end-of-day review?

End-of-day consolidation keeps non-triageable or general items in a summary bucket. This approach rolls up unhandled messages into a later summary rather than forcing immediate routing decisions during batch processing.

Do I need a managed TaskFlow lifecycle to route inbox items with state management?

Yes, routing inbox items requires a managed TaskFlow lifecycle with persisted stateJson. The workflow follows a structured classify, wait, resume, route, and finish sequence to handle each batch deterministically.

Can I use workflow orchestration to batch process personal and business messages differently?

Workflow orchestration sends business messages into a waiting state for an outside answer while immediately notifying the owner for personal items. This intent-based classification separates handling paths within the same batch.