taskflow-inbox-triage

Name: taskflow-inbox-triage
Author: openclaw

Triage inbox messages, route intents, track replies, and generate follow-up summaries.

Stars

★ 386,615

Source

GitHub

Updated

2026-08-18

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 386.6k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "taskflow-inbox-triage" skill from askskill:
1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/skills/taskflow-inbox-triage/SKILL.md
2. Save it as ~/.claude/skills/taskflow-inbox-triage/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Client Email Triage

Prompt

Please classify today’s inbox emails by intent: reply now, delegate, waiting for client reply, or archive only, and suggest the next action for each email.

Expected

A grouped email list by intent with priorities and recommended next actions.

Waiting-for-Reply Tracking

Prompt

Organize all sent emails that are still awaiting replies, listing send time, recipient, and subject, and mark which ones need follow-up within 48 hours.

Expected

A waiting-for-reply follow-up list with overdue alerts and suggested follow-up order.

Periodic Communication Summary

Prompt

Based on this week’s inbox and sent emails, summarize key communication topics, open items, completed items, and tasks to continue next week.

Expected

A concise weekly communication summary highlighting key items and follow-up actions.

// docs

TaskFlow inbox triage

This is a concrete example of how to think about TaskFlow without turning the core runtime into a DSL.

Goal

Triage inbox items with one owner flow:

business -> post to Slack and wait for reply
personal -> notify the owner now
everything else -> keep for end-of-day summary

Pattern

Create one flow for the inbox batch.
Run one detached task to classify new items.
Persist the routing state in stateJson.
Move to waiting only when an outside reply is required.
Resume the flow when classification or human input completes.
Finish when the batch has been routed.

Suggested `stateJson` shape

{
  "businessThreads": [],
  "personalItems": [],
  "eodSummary": []
}

Suggested waitJson when blocked on Slack:

{
  "kind": "reply",
  "channel": "slack",
  "threadKey": "slack:thread-1"
}

Minimal runtime calls

const taskFlow = api.runtime.tasks.flow.fromToolContext(ctx);

const created = taskFlow.createManaged({
  controllerId: "my-plugin/inbox-triage",
  goal: "triage inbox",
  currentStep: "classify",
  stateJson: {
    businessThreads: [],
    personalItems: [],
    eodSummary: [],
  },
});

const child = taskFlow.runTask({
  flowId: created.flowId,
  runtime: "acp",
  childSessionKey: "agent:main:subagent:classifier",
  task: "Classify inbox messages",
  status: "running",
  startedAt: Date.now(),
  lastEventAt: Date.now(),
});

if (!child.created) {
  throw new Error(child.reason);
}

const waiting = taskFlow.setWaiting({
  flowId: created.flowId,
  expectedRevision: created.revision,
  currentStep: "await_business_reply",
  stateJson: {
    businessThreads: ["slack:thread-1"],
    personalItems: [],
    eodSummary: [],
  },
  waitJson: {
    kind: "reply",
    channel: "slack",
    threadKey: "slack:thread-1",
  },
});

if (!waiting.applied) {
  throw new Error(waiting.code);
}

const resumed = taskFlow.resume({
  flowId: waiting.flow.flowId,
  expectedRevision: waiting.flow.revision,
  status: "running",
  currentStep: "route_items",
  stateJson: waiting.flow.stateJson,
});

if (!resumed.applied) {
  throw new Error(resumed.code);
}

taskFlow.finish({
  flowId: resumed.flow.flowId,
  expectedRevision: resumed.flow.revision,
  stateJson: resumed.flow.stateJson,
});