taskflow-inbox-triage

Classify inbox messages by intent and route them to Slack, notifications, or summaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage inbox messages by intent and route them to the appropriate follow-up actions.

Core Features & Use Cases

  • Create one flow for the inbox batch.
  • Run a detached classifier to categorize new items.
  • Persist routing state in stateJson and resume when needed.
  • Route items to Slack with a waiting state for replies, notify owners immediately for personal items, or roll non-critical items into an end-of-day summary.
  • Finish when all items are routed and the batch is completed.

Quick Start

Initialize a new inbox-triage flow, run a classifier, and route messages according to intent in a single batch.

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

Inbox triage automation classifies incoming messages by intent and routes them to downstream actions like Slack posts, owner notifications, or end-of-day summaries. You create a single flow for the batch, run a detached classifier, and persist routing state in stateJson.

How does stateJson persistence work when waiting for external input during message routing?

StateJson persistence saves the routing state of your inbox flow while waiting for external input, such as Slack replies. The flow resumes automatically after completion and finalizes once all items are routed and the batch is completed.

Can I use a detached classifier to categorize inbox items into business, personal, and other categories?

Yes, you can run a detached classifier to categorize new inbox items into business, personal, and other categories. This classification drives the conditional routing to appropriate downstream actions based on the detected intent.

What is the best way to handle personal inbox items that need immediate action?

For personal inbox items requiring immediate action, the routing flow triggers immediate owner notifications. Non-critical items are instead rolled into an end-of-day summary, ensuring urgent tasks are prioritized.

Does this inbox triage workflow support Slack replies within the routing flow?

Yes, the workflow routes items to Slack with a waiting state and supports waiting on external input. It resumes after receiving Slack replies and completes finalization when all batch items are fully routed.