taskflow-inbox-triage

Name: taskflow-inbox-triage
Availability: InStock
Author: wuv-dreamguide

Classify inbox items by intent and route actions automatically.

Updated Apr 21, 2026

Search Tags:#automation #workflow #routing #inbox #triage #taskflow

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage incoming inbox items by intent to route actions automatically, request further input when needed, and summarize unresolved items at day end.

Core Features & Use Cases

A single owner flow that classifies items and routes them to immediate notifications, awaiting external replies, or end-of-day summaries.
Demonstrates state management with stateJson, waitJson, and flow control for resume/finish.
Provides a concrete pattern for building TaskFlow-based inbox triage in real-world workflows.

Quick Start

Create a TaskFlow inbox-triage flow, classify messages, and route them according to intent.

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 messages by intent?▼

Inbox triage automation uses a single-owner flow that classifies incoming items by intent and routes actions automatically, defers them for external input, or summarizes unresolved items at day end.

How does workflow state management work when awaiting external replies?▼

Workflow state management uses stateJson to track classification and waitJson to set a waiting state, pausing the flow until external input arrives, then resuming and finishing the flow automatically.

Can I generate end-of-day summaries for unresolved inbox items?▼

Yes, you can generate end-of-day summaries by routing unresolved inbox items to a summary task within the triage flow, ensuring deferred or unclassified messages are collected for later follow-up.

What is the best way to handle inbox routing for a single-owner workflow?▼

The best way to handle single-owner inbox routing is applying a classification task that evaluates message intent and directs items to immediate notifications, waiting states, or end-of-day summaries based on the result.

Does this inbox triage pattern support pausing and resuming workflows?▼

Yes, the inbox triage pattern supports pausing and resuming workflows by setting a waiting state with waitJson, then automatically resuming the flow when the required external input arrives.