Command
tendem-result
Fetch and present a completed Tendem task's result (markdown + files)
@tolokaInstall CommandSales
Command
/tendem-status
Check on a Tendem task and advance it (poll cleanly, don't busy-loop)
Install
> /plugin marketplace add toloka/tendem-mcp > /plugin install tendem@tendem-mcp
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/tendem-status
Context preview
What this command does when you run it.
Check on a Tendem task and advance it (poll cleanly, don't busy-loop)
Command definition
tendem-status.mdname: tendem-status
description: Check on a Tendem task and advance it (poll cleanly, don't busy-loop)
argument-hint: [task_id — optional; omit to pick from your recent tasks]
Check the status of a Tendem task and take the next correct step.
- If a `task_id` is given in **$ARGUMENTS**, use it. Otherwise call
`list_tasks` and either use the obvious in-flight task or ask the user which one.
- Call `get_task(task_id, wait_for_change_seconds=30)` and act on the returned
`next_action` (per the `tendem-tasks` skill):
- `awaiting_tendem_work` → it's still working. Report where it stands and do
NOT sit re-polling. Offer the user two ways to wait: (a) you spawn the `tendem-watcher` agent in the background — give it the `task_id`, a poll interval (default 1 hour), and it reports back the moment the task needs them; or (b) they simply ask again later ("how's the Tendem task doing?" or `/tendem-status`) — the task lives on Tendem's side, nothing is lost between sessions.
- `await_input` → read the new chat and answer via `send_message` (or escalate).
- `await_user_approval` → call `get_contract(task_id)` for the full scope +
price, surface both; approve only with the user's go-ahead.
- `await_user_topup` → give the user the `topup_url`.
- `fetch_result` → run `/tendem-result` (or call `get_task_result`).
- `done` → nothing left; summarize the outcome.
Summarize where the task stands and what happens next in plain language.
Read more
name: tendem-status description: Check on a Tendem task and advance it (poll cleanly, don't busy-loop) argument-hint: [task_id — optional; omit to pick from your recent tasks]
Check the status of a Tendem task and take the next correct step.
- If a `task_id` is given in **$ARGUMENTS**, use it. Otherwise call
`list_tasks` and either use the obvious in-flight task or ask the user which one.
- Call `get_task(task_id, wait_for_change_seconds=30)` and act on the returned
`next_action` (per the `tendem-tasks` skill):
- `awaiting_tendem_work` → it's still working. Report where it stands and do
NOT sit re-polling. Offer the user two ways to wait: (a) you spawn the `tendem-watcher` agent in the background — give it the `task_id`, a poll interval (default 1 hour), and it reports back the moment the task needs them; or (b) they simply ask again later ("how's the Tendem task doing?" or `/tendem-status`) — the task lives on Tendem's side, nothing is lost between sessions.
- `await_input` → read the new chat and answer via `send_message` (or escalate).
- `await_user_approval` → call `get_contract(task_id)` for the full scope +
price, surface both; approve only with the user's go-ahead.
- `await_user_topup` → give the user the `topup_url`.
- `fetch_result` → run `/tendem-result` (or call `get_task_result`).
- `done` → nothing left; summarize the outcome.
Summarize where the task stands and what happens next in plain language.
Other commands on tendem-mcp.
@tolokaInstall CommandCommand
tendem-task
Submit a new task to Tendem (hybrid AI + human experts) and drive it through scoping
@tolokaInstall Command