taskflow-inbox-triage

Route inbox messages to Slack, owner notifications, or end-of-day summaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage inbox messages by intent with a single owner flow: route business items to Slack, notify the owner for personal items, and keep everything else for an end-to-end daily summary.

Core Features & Use Cases

  • Create one flow for the inbox batch and run a detached classifier to decide routing.
  • Persist flow state and move items to a waiting state when external input is required.
  • Resume, route, and finish flows to complete end-to-end triage and reporting.

Quick Start

Create a new inbox-triage flow for a batch of messages, classify each item by intent, and route business items to Slack, notify the owner for personal items, and hold everything else for the 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 to route business and personal messages differently?

Inbox triage automation routes business items to Slack, notifies the owner for personal items, and holds the rest for an end-of-day summary. A detached classification step determines the routing intent for each message in a batch.

What is the best way to handle external replies during an automated workflow?

Automated workflows handle external replies by moving items to a waiting state. Flow state persists until external input is received, allowing the orchestration runtime to resume and finish the triage process accurately.

How does state management work for message orchestration in TaskFlow?

State management in TaskFlow persists the flow state across the inbox triage lifecycle. It supports resume and finish operations, ensuring messages waiting for external replies are tracked until the end-of-day summary is generated.

Can I process batches of incoming messages and summarize them at day end?

Yes, you can process batches of incoming messages by classifying each item by intent. Items not requiring immediate action or external replies are collected and held for an end-of-day summary report.

Do I need any external dependencies to run the TaskFlow inbox triage flow?

No external dependencies are required to run the TaskFlow inbox triage flow. The skill operates independently within the TaskFlow runtime to classify, route, and summarize messages using persistent state management.