taskflow-inbox-triage

Route inbox messages by intent into notifications, waiting threads, or summaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you triage an inbox efficiently by routing messages to different outcomes based on intent, so some items get notified immediately, others wait for external replies, and the rest roll into a later summary.

Core Features & Use Cases

  • Intent-based routing: Classify inbox items into categories like business, personal, and everything else.
  • Mixed synchronous and asynchronous handling: Immediately notify for personal items while using waiting states for business items that require an external reply.
  • State-driven resumption: Persist routing progress in stateJson and resume the flow when classification or human input completes.
  • End-of-day batching: Collect items that don’t require immediate action for a later summary.

Quick Start

Use the taskflow-inbox-triage skill to triage an inbox batch into business, personal, and end-of-day summary routes by classifying items, waiting on Slack replies when needed, and then finishing the batch when routing is complete.

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 by detected intent?

Inbox triage automation routes messages by classifying intent into categories like business or personal, then directing items to immediate notifications, reply-waiting threads, or end-of-day summary buckets.

What is the best way to handle asynchronous message routing waiting for external replies?

Asynchronous message routing uses waiting states to pause processing until an external reply arrives. It persists routing progress and resumes the flow once the expected reply or human input completes.

How does state-driven workflow orchestration resume an inbox batch after waiting on Slack replies?

State-driven workflow orchestration resumes an inbox batch by persisting routing progress in stateJson. It waits on Slack reply channels and resumes with expected revisions when replies arrive.

Can I batch process an inbox and defer non-urgent items into an end-of-day summary?

Yes, you can batch process an inbox and defer non-urgent items. Intent classification identifies items requiring no immediate action and routes them into an end-of-day summary bucket.

How do I manage mixed synchronous and asynchronous message handling in a single workflow?

Mixed message handling manages synchronous and asynchronous flows by immediately notifying for urgent items while using waiting states for items requiring external tool or human replies before resuming.

What is required to implement intent classification for batched inbox processing?

Implementing intent classification for batched inbox processing requires a managed flow with persisted stateJson, explicit waiting via waitJson for reply channels, and resuming with expected revisions.