taskflow-inbox-triage

Classify TaskFlow inbox items and route them by owner and channel.

1|Updated Mar 6, 2026

Search Tags:#routing #asynchronous #state-management #workflow-orchestration #taskflow #inbox-triage

Ready to run

npx skills add https://github.com/zhcndoc/openclaw --skill taskflow-inbox-triage-zhcndoc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: taskflow-inbox-triage
Source: https://github.com/zhcndoc/openclaw/tree/main/skills/taskflow-inbox-triage
Command: npx skills add https://github.com/zhcndoc/openclaw --skill taskflow-inbox-triage-zhcndoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage inbox items with one owner flow: business items get posted to Slack and await replies, personal items are surfaced to their owners immediately, and everything else is held for an end-of-day summary.

Core Features & Use Cases

One owner flow per inbox batch to classify items, route them to appropriate channels, and manage awaiting responses.
Persist and resume progress using stateJson and waitJson to coordinate asynchronous interactions.
Automatically generate end-of-day summaries for unhandled items and ensure reliable visibility across teams.

Quick Start

Create and run a TaskFlow inbox-triage instance to classify a batch of messages and route them according to the described rules.

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 to route business items to Slack and personal items to owners?▼

Automated inbox triage classifies incoming messages and routes business items to Slack channels, personal items directly to owners, and miscellaneous items for end-of-day review using a deterministic state workflow.

How does asynchronous state management work for inbox message routing?▼

Asynchronous state management uses stateJson and waitJson to persist progress, allowing the triage workflow to pause while awaiting replies and resume stateful progression once responses arrive.

What is the best way to handle unhandled inbox items for an end-of-day summary?▼

End-of-day summaries automatically collect unhandled miscellaneous items from your inbox, ensuring reliable visibility across teams by holding non-urgent messages for a consolidated daily review.

Can I use workflow orchestration to coordinate create, run, resume, and finish calls for message classification?▼

Workflow orchestration coordinates create, run, resume, and finish calls to manage deterministic message classification, enabling stateful progression through routing rules and awaiting replies.

Does TaskFlow inbox triage support team inboxes where messages post to multiple channels?▼

TaskFlow inbox triage applies to team inboxes by implementing a one-owner flow per batch, routing business items to Slack channels while notifying personal item owners immediately.

What are the limitations of using deterministic workflow orchestration for inbox triage?▼

Deterministic workflow orchestration requires strict stateJson and waitJson coordination, meaning routing rules are fixed per batch and asynchronous awaiting replies must follow the defined stateful progression without dynamic deviation.