taskflow-inbox-triage

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage inbox items by applying targeted routing based on intent, enabling immediate notifications, delayed decisions, or consolidated summaries.

Core Features & Use Cases

  • One-owner TaskFlow for inbox batches that classifies items and routes them to the right channels.
  • Persisted state allows resuming after external input or delayed decisions.
  • Detach and resume patterns support real-time and end-of-day workflows.

Quick Start

Triaging a batch of inbox messages by classifying items and routing business items to Slack, personal items for immediate notification, and others to an 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 automatically triage an inbox batch and route messages by intent?

Inbox triage automatically classifies incoming messages by intent and routes them to appropriate channels for immediate notification, delayed decisions, or consolidated summaries. This works by applying targeted routing rules to batch inbox items.

Can I pause inbox processing and resume it later after receiving external input?

Yes, you can pause inbox processing and resume it later. Persisted state allows the workflow to resume after external input or delayed decisions, supporting both real-time and end-of-day workflows using detach and resume patterns.

What is the best way to separate urgent messages from daily summaries in a batch workflow?

Separating urgent messages from daily summaries is achieved by classifying items based on intent. Business items route to Slack, personal items trigger immediate notification, and remaining items contribute to an end-of-day summary.

Does TaskFlow routing support state persistence for delayed decisions?

TaskFlow routing supports state persistence for delayed decisions. It satisfies runtime flow orchestration requirements by maintaining state across external inputs, allowing workflows to resume where they left off.

Why use conditional routing instead of a single pass for inbox batch processing?

Conditional routing enables targeted handling of inbox items based on their classified intent. Instead of a single pass, it routes messages to the right channels for immediate notification, delayed decisions, or consolidated summaries, optimizing workflow efficiency.