Task And Inbox Agent Workflow
Rule
Read the user's visible context with view-screen before acting on anything
referential, capture ambiguous input into the inbox rather than the task list,
and never delete without explicit confirmation in chat.
Capture
- Capture in chat →
create-inbox-item by default; use create-task only when
the user asks to add directly to the task list.
Read the screen before ambiguous edits
- Call
view-screen before ambiguous edits when the user says "this task",
"these tasks", "this inbox item", or "the list".
- On
/tasks or /inbox, view-screen returns list (with items), optional
selectedItem (inListSnapshot), and optional selection
(selectedItems, selectedIdsNotInVisibleList) when bulk-select is active.
- Prefer
selection.selectedItems when the user has UI rows selected; fall back
to selectedItem for a single deep-link highlight.
- Use
navigation.includeDone and list from view-screen to match what the
user sees on /tasks.
Showing the list from another view
- When the user asks to see, review, or manage tasks while
navigation.view is
not tasks, call render-task-list-inline instead of navigating away. Pass
includeDone: true when completed tasks should be included. The widget can
add tasks and toggle completion through the existing task actions.
- When the user is already on
/tasks, use view-screen and the native task
list for task-list context unless the user explicitly asks for an inline
widget.
Reordering
- Use
reorder-tasks with the same includeDone flag when moving tasks in the
visible list.
- Use
reorder-inbox-items with the inbox item ids in the desired
top-to-bottom order.
AI task routing
- Call
suggest-task-route for a queue suggestion, optional choice probability and confidence, and urgency probability. It reads an existing Queue field or uses the default Work, Personal, and Other options without changing the task.
- After the user accepts the queue, call
apply-task-route with its name. The action creates the Queue field on first use. Urgency probability is a suggestion, not a stored priority.
Deleting
delete-task, bulk-delete-tasks, delete-inbox-item, and
bulk-delete-inbox-items only after explicit user confirmation in chat.
Task detail extension slot
The task detail panel exposes tasks.task-detail.bottom as an ExtensionSlot
with slotContext containing taskId, title, done, and fieldValues.
Related Skills
- custom-fields — custom field definitions, values, and task-card visibility.
- action-reference — the full action table with HTTP methods and arguments.
- store-conventions — the server store functions these actions call.
1---2name: task-inbox-workflow3description: >-4 How the agent captures, reads, edits, reorders, and deletes tasks and inbox5 items using view-screen context. Use when the user mentions "this task",6 "these tasks", "this inbox item", or "the list", or asks to capture, show,7 review, reorder, complete, or delete tasks or inbox items.8metadata:9 source: https://skillmd.com/skills/builderio/task-inbox-workflow10---1112# Task And Inbox Agent Workflow1314## Rule1516Read the user's visible context with `view-screen` before acting on anything17referential, capture ambiguous input into the inbox rather than the task list,18and never delete without explicit confirmation in chat.1920## Capture2122- Capture in chat → `create-inbox-item` by default; use `create-task` only when23 the user asks to add directly to the task list.2425## Read the screen before ambiguous edits2627- Call `view-screen` before ambiguous edits when the user says "this task",28 "these tasks", "this inbox item", or "the list".29- On `/tasks` or `/inbox`, `view-screen` returns `list` (with `items`), optional30 `selectedItem` (`inListSnapshot`), and optional `selection`31 (`selectedItems`, `selectedIdsNotInVisibleList`) when bulk-select is active.32- Prefer `selection.selectedItems` when the user has UI rows selected; fall back33 to `selectedItem` for a single deep-link highlight.34- Use `navigation.includeDone` and `list` from `view-screen` to match what the35 user sees on `/tasks`.3637## Showing the list from another view3839- When the user asks to see, review, or manage tasks while `navigation.view` is40 not `tasks`, call `render-task-list-inline` instead of navigating away. Pass41 `includeDone: true` when completed tasks should be included. The widget can42 add tasks and toggle completion through the existing task actions.43- When the user is already on `/tasks`, use `view-screen` and the native task44 list for task-list context unless the user explicitly asks for an inline45 widget.4647## Reordering4849- Use `reorder-tasks` with the same `includeDone` flag when moving tasks in the50 visible list.51- Use `reorder-inbox-items` with the inbox item ids in the desired52 top-to-bottom order.5354## AI task routing5556- Call `suggest-task-route` for a queue suggestion, optional choice probability and confidence, and urgency probability. It reads an existing Queue field or uses the default Work, Personal, and Other options without changing the task.57- After the user accepts the queue, call `apply-task-route` with its name. The action creates the Queue field on first use. Urgency probability is a suggestion, not a stored priority.5859## Deleting6061- `delete-task`, `bulk-delete-tasks`, `delete-inbox-item`, and62 `bulk-delete-inbox-items` only after explicit user confirmation in chat.6364## Task detail extension slot6566The task detail panel exposes `tasks.task-detail.bottom` as an `ExtensionSlot`67with `slotContext` containing `taskId`, `title`, `done`, and `fieldValues`.6869## Related Skills7071- **custom-fields** — custom field definitions, values, and task-card visibility.72- **action-reference** — the full action table with HTTP methods and arguments.73- **store-conventions** — the server store functions these actions call.