taskflow-inbox-triage

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and route inbox items automatically based on intent, enabling business items to post to Slack and await replies, personal items to notify owners immediately, and non-urgent items to be rolled into an end-of-day summary.

Core Features & Use Cases

  • One flow handles the entire batch of inbox items.
  • Detach a classifier task to categorize items and persist routing state in stateJson for resuming later.
  • Route items into waiting state when external input is required, resume on completion, and finish with a consolidated state.

Quick Start

Create one flow for the inbox batch, run a classifier task, and route messages based on their intent using the stateJson.

Frequently Asked Questions about taskflow-inbox-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically route and triage inbox items based on message intent?

To triage inbox items automatically, this Skill classifies message intents and routes business items to Slack, personal items to immediate owner notification, and others to an end-of-day summary. It persists routing state in stateJson to resume workflows later.

How does workflow routing handle waiting for external replies from Slack?

Workflow routing handles external replies by placing routed business items into a waiting state and persisting progress in stateJson. When the external input arrives, the flow resumes execution and completes the task with a consolidated final state.

Can I process a batch of inbox messages in a single workflow flow?

Yes, you can process an entire batch of inbox items in one flow. The Skill detaches a classifier task to categorize the batch and routes all messages based on their detected intent using the stateJson routing state.

What is the best way to classify and roll up non-urgent messages for an end-of-day summary?

The best way to classify non-urgent messages is to use the intent classifier to identify them during the triage flow. The Skill preserves these items and rolls them up into a consolidated end-of-day summary instead of triggering immediate notifications.

Do I need any external dependencies to use the TaskFlow inbox triage routing?

No external dependencies are required to run the TaskFlow inbox triage routing. The Skill operates independently using the runtime API for flow creation, task execution, waiting for external replies, and completion.

Why does my workflow need to persist routing state in stateJson?

Your workflow needs to persist routing state in stateJson to save the classification and routing status of inbox items. This allows the flow to pause while waiting for external replies and reliably resume later without losing progress.