Guide · Agent skill
How to use the TaskFlow Inbox Triage agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The TaskFlow Inbox Triage skill (taskflow-inbox-triage) is an example that shows how an agent can sort a batch of inbox messages by intent and route each group differently. It is written for developers who want a worked reference for flow, task and wait states on the Brigade TaskFlow runtime. After this guide you will know what the skill teaches, how to install it, how to ask for it in plain language, and where its limits are.
TaskFlow Inbox Triagespinabot/brigade · MIT Download the skill Quick start
- 1Download the ZIP. Get the taskflow-inbox-triage ZIP from the skill page.
- 2Install the skill. Unzip into ~/.claude/skills/ or a project's .claude/skills/, or upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
- 3Confirm your runtime. Make sure the Brigade TaskFlow runtime (api.runtime.tasks.flow) is available, since the example code depends on it.
- 4Ask for triage in plain words. Describe the routing you want: business to Slack with a wait, personal now, everything else for a summary.
- 5Review the flow and state. Check the stateJson and waitJson shapes the agent proposes against the SKILL.md examples.
- 6Test before connecting live channels. Run the logic on sample messages first, since misclassification can send content to the wrong place.
What an agent skill is and what this one does
An agent skill is a folder with a SKILL.md file that gives an agent instructions for a specific kind of task. This skill covers inbox triage: sorting messages by intent so each kind gets different treatment.
The pattern routes items in three ways. Business messages are posted to Slack and the flow pauses until someone replies. Personal items notify the owner right away. Everything else is kept for an end-of-day summary.
- Create one flow for an inbox batch.
- Run one background task to classify new items.
- Store routing state in stateJson.
- Move to waiting only when an outside reply is required.
- Resume when classification or human input completes, then finish once the batch is routed.
Install the taskflow-inbox-triage skill
Download the ZIP from the skill page. Unzip it into ~/.claude/skills/ for a personal install, or into a project's .claude/skills/ folder to share it within that project.
You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.
Trigger the skill with a natural request
The skill's description says to use it when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary. Ask for that kind of work in plain words, for example: triage my inbox batch so business messages go to Slack and wait for a reply, personal items notify me now, and the rest go into an end-of-day summary.
Expect the agent to lay out the flow and state it would use. The file is a pattern, so it does not connect to your mail provider on its own.
Read the example code and state shapes
The SKILL.md file includes a suggested stateJson shape with businessThreads, personalItems and eodSummary lists. It also shows a waitJson object for a Slack reply, with kind set to reply, channel set to slack and a threadKey.
The minimal runtime calls use api.runtime.tasks.flow.fromToolContext(ctx), then createManaged, runTask, setWaiting, resume and finish. Each write passes an expectedRevision so updates are checked against the current flow revision. The file also points to skills/taskflow/examples/inbox-triage.lobster as a related example.
const taskFlow = api.runtime.tasks.flow.fromToolContext(ctx);Requirements and safety notes
You need the Brigade TaskFlow runtime (api.runtime.tasks.flow) to run the example code. Posting business threads assumes a Slack integration, which the file implies but does not configure.
The skill runs no scripts and uses no network access itself. Because it routes messages to Slack and notifications, a misclassified message could expose private content or reach the wrong person. Review the classification logic before using it on a sensitive inbox.
- Runtime: Brigade TaskFlow (api.runtime.tasks.flow)
- Slack integration: needed for business threads, not included in the file
- Scripts: none
- Network: none in the skill itself
Tips for adapting the pattern
Treat this as a starting point. Keep the separation between classification, waiting and routing so each stage can be tested on its own.
Always pass the current revision when you update a flow, and handle the failure branches shown in the example rather than ignoring them.
- Test classification on sample messages before connecting Slack.
- Keep the wait condition specific, such as one threadKey per business thread.
- Check the end-of-day summary contents against what you expect each day.
What people use it for
- Developers building a plugin that needs a worked example of flow, task and wait states.
- Teams designing triage that must pause for an external Slack reply before continuing.
- Routing personal items to the owner immediately while batching other items for an end-of-day summary.
- Studying how expectedRevision guards updates to a flow's state.
Frequently asked questions
Is the taskflow-inbox-triage skill free to use?
The skill is listed under the MIT licence. The source does not state any price, so check the skill page for licence terms before reuse.
Does this skill read my email automatically?
No. The file describes a pattern and example code. It does not connect to any mail provider, so you would need to supply the message source yourself.
What do I need to run this skill?
You need the Brigade TaskFlow runtime (api.runtime.tasks.flow) to run the example code. Posting business threads also requires a Slack integration, which the file implies but does not set up.
Does the skill run scripts or use the network?
According to the listing, it runs no scripts and uses no network access. The Slack and notification steps depend on the runtime and integrations you connect.
Where do I install the skill folder?
Unzip the downloaded ZIP into ~/.claude/skills/ for a personal install or into a project's .claude/skills/ folder. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.
Is this a good alternative to a ready-made inbox assistant?
Not if you want something that works out of the box. It is a developer reference for structuring multi-step triage on TaskFlow. If you need a finished assistant that connects to your mail, choose a product built for that purpose.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits developers building on the Brigade TaskFlow runtime who want a clear example of flow, task and wait states. It is not a ready-to-run email assistant, and it should not be pointed at a sensitive inbox without careful review of how messages are classified and routed.
Download the skill