taskflow-inbox-triage

Classify inbox items and route them to Slack or summaries via TaskFlow.

Updated Apr 7, 2026

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

Ready to run

npx skills add https://github.com/Luzzer/Kraken --skill taskflow-inbox-triage-luzzer

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This pattern provides a structured way to triage inbox items using a single TaskFlow, allowing business messages to be routed to Slack for replies, personal items to be triggered for immediate notifications, and all other messages to be rolled into an end-of-day summary.

Core Features & Use Cases

Create one flow for the inbox batch and manage it end-to-end.
Run a detached classifier task to categorize items.
Persist routing state in stateJson for recovery and replay.
Move to waiting only when an external reply is required, then resume when complete.
Finish the flow when the batch has been routed and summarized.

Quick Start

Create one inbox-triage flow, classify items, wait for external replies when needed, route items accordingly, and finish the batch with a 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 business messages to Slack?▼

Inbox triage automation routes business messages to Slack for replies, notifies owners for personal items, and holds others for end-of-day summaries. It uses a single TaskFlow to classify and manage mixed message batches end-to-end.

How does workflow routing handle waiting for external replies before resuming?▼

Workflow routing uses waitJson to pause state and moves the flow to waiting only when external input is required. Once the reply is complete, the resume function continues the task sequence without losing the persisted routing context.

What is the best way to batch classify shared inbox items for end-of-day summaries?▼

Batch classifying shared inbox items is handled by a detached classifier task that categorizes mixed messages. Unrouted items are then collected and summarized when the flow finishes, ensuring no message is missed.

Can I persist routing state for inbox automation to recover from interruptions?▼

Yes, inbox automation persists routing state in stateJson during classification and sequencing. This allows recovery and replay of the triage flow if the process is interrupted before reaching the final summary.

Does TaskFlow inbox triage support managing runtime state for mixed message types?▼

TaskFlow inbox triage fully supports runtime state management for mixed message types via stateJson. It sequences operations end-to-end through createManaged, runTask, setWaiting, resume, and finish to ensure proper routing.