Taskflow Inbox Triage
PassAudited by ClawScan on May 13, 2026.
Overview
This is an instruction-only TaskFlow example with no installable code or credentials, though users should notice that the example demonstrates Slack notifications, a detached classifier task, and persisted triage state.
This skill appears safe as an instructional example. If adapting it for real inboxes, be careful about what gets posted to Slack, what inbox data is stored in TaskFlow state, and how detached classifier tasks are monitored and stopped.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A real implementation could notify people or post into Slack based on message classification.
The example routes some inbox items to external or user-visible notifications. This is disclosed and central to the triage pattern, but could create messages if implemented with real tools.
- business → post to Slack and wait for reply - personal → notify the owner now
Confirm the destination, content, and approval policy before using this pattern with live Slack or notification tools.
Inbox-related routing information may be retained beyond a single prompt or step.
The pattern stores flow state that may include inbox classifications, message identifiers, or summaries so the workflow can resume later.
Persist the routing state in `stateJson`.
Store only the minimum needed identifiers or summaries, avoid sensitive message content when possible, and define retention/cleanup behavior in any real implementation.
A child task could continue processing while the parent flow waits or resumes if a real implementation does not manage it carefully.
The example demonstrates spawning a detached child classification task. It is scoped to classifying inbox messages, but detached work should remain tracked and bounded.
Run one detached task to classify new items.
Keep detached tasks limited to the stated classification job, track their status, and ensure they are cancelled or completed when the flow ends.