taskflow-inbox-triage

Routes inbox items by intent to immediate notification, waiting for external replies, or summaries using TaskFlow runtime and waitJson/stateJson.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill taskflow-inbox-triage-seasonmac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskflow-inbox-triage
Source: https://github.com/seasonmac/Full-Scene-Agents/tree/main/openclaw/skills/taskflow-inbox-triage
Command: npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill taskflow-inbox-triage-seasonmac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage inbox items by intent and route them to the appropriate follow-up path, enabling immediate notification, waiting for external input, or rolling results into an end-of-day summary.

Core Features & Use Cases

  • One-flow inbox triage: Create a single owner flow that classifies items and routes them based on intent.
  • Detachable classification step: Run a separate classification task to determine routing without blocking the main flow.
  • Stateful routing & waiting: Persist state in stateJson and support waiting for external replies via waitJson.

Quick Start

Create a TaskFlow inbox triage pattern that routes messages by intent, notifies immediately for personal items, waits for external replies when needed, and aggregates remaining items into an end-of-day summary.

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

Automate inbox triage by classifying items by intent and routing them to appropriate follow-up paths. You can configure a flow to notify owners immediately, wait for external replies, or aggregate items into an end-of-day summary.

What is the best way to handle inbox items that need external responses?

Handle inbox items needing external responses by persisting their state in stateJson and using waitJson to pause the workflow. This stateful routing mechanism holds the item until an external reply is received before finalizing the follow-up path.

Can I run a separate classification task without blocking the main inbox workflow?

Yes, you can run a detachable classification step to determine routing without blocking the main flow. This allows the inbox triage workflow to continue processing other items while classification occurs independently.

How does an end-of-day summary rollup work for inbox routing?

An end-of-day summary rollup aggregates inbox items that do not require immediate notification or external responses. The routing workflow classifies these items and compiles them into a single summary for end-of-day review.

Do I need a specific runtime to persist state and wait for external input during triage?

You need a TaskFlow runtime to persist state in stateJson and support waiting for external replies via waitJson. This environment manages the stateful routing required to pause and resume inbox triage workflows.