taskflow-inbox-triage

Classify and route inbox messages using a single TaskFlow flow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TaskFlow inbox triage helps teams automatically categorize and route incoming messages based on intent, reducing manual triage effort and speeding up response times.

Core Features & Use Cases

  • Single inbox flow to classify and route messages.
  • Detaches tasks to external systems (e.g., Slack) and waits for replies.
  • Supports end-of-day summary aggregation and resume ability.

Quick Start

Create a TaskFlow inbox-triage flow and start the classification process.

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 message routing for team inboxes?

Automate message routing for team inboxes by classifying and routing incoming messages through a single TaskFlow flow, which categorizes items by intent and sends immediate Slack notifications or end-of-day summaries.

What is the best way to triage Slack inbox messages automatically?

The best way to triage Slack inbox messages automatically is using a TaskFlow runtime that detaches tasks to external systems, applies state management with stateJson, and waits for replies to resume or finish the lifecycle.

How do I set up an end-of-day summary for inbox triage?

Set up an end-of-day summary for inbox triage by configuring a TaskFlow flow with waitJson and resume/finish lifecycle states, allowing the system to aggregate routed business and personal items into a single daily digest.

Do I need a TaskFlow runtime to automate inbox classification?

Yes, you need a TaskFlow runtime to automate inbox classification because the Skill relies on a single flow and state management with stateJson, waitJson, and resume/finish lifecycle to process and route messages.

Can I route business and personal inbox items differently using automation?

Yes, you can route business and personal inbox items differently by applying classification within the TaskFlow flow, which detaches tasks to external systems and triggers owner alerts or end-of-day summaries based on the message intent.