Command
tendem-result
Fetch and present a completed Tendem task's result (markdown + files)
@tolokaInstall CommandSales
Command
/tendem-task
Submit a new task to Tendem (hybrid AI + human experts) and drive it through scoping
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-task
Context preview
What this command does when you run it.
Submit a new task to Tendem (hybrid AI + human experts) and drive it through scoping
Command definition
tendem-task.mdname: tendem-task
description: Submit a new task to Tendem (hybrid AI + human experts) and drive it through scoping
argument-hint: <what you want a human expert to do>
Submit a new Tendem task from this instruction: **$ARGUMENTS**
Follow the `tendem-tasks` skill. Fidelity first:
1. Call `create_task` **now** — `description` is the user's instruction above, passed as faithfully as possible. Add only context the user actually stated (input files by name, a deadline if one was given). Do NOT expand it into a synthesized brief, and do NOT pre-ask the user clarifying questions — scoping is Tendem's job. Derive a short `name` (≤120 chars) and reuse a stable `conversation_id` for this conversation. 2. If the instruction references local files, upload them immediately after creating the task (`get_file_upload_url` + the skill's `scripts/tendem-upload.sh`, then the naming `send_message`). 3. Scoping loop: poll with `get_task(task_id, wait_for_change_seconds=30)`, answer Tendem's questions from conversation context via `send_message`, escalate to the user only when the answer isn't in context or scope/deliverables/deadline are at stake. 4. Stop when the quote is ready (`next_action=await_user_approval`): call `get_contract(task_id)` for the full scope + price, show the user both, and wait for their explicit go-ahead before `approve_task`.
Report the `task_id` in your reply so it can be referenced later.
Read more
name: tendem-task description: Submit a new task to Tendem (hybrid AI + human experts) and drive it through scoping argument-hint: <what you want a human expert to do>
Submit a new Tendem task from this instruction: **$ARGUMENTS**
Follow the `tendem-tasks` skill. Fidelity first:
1. Call `create_task` **now** — `description` is the user's instruction above, passed as faithfully as possible. Add only context the user actually stated (input files by name, a deadline if one was given). Do NOT expand it into a synthesized brief, and do NOT pre-ask the user clarifying questions — scoping is Tendem's job. Derive a short `name` (≤120 chars) and reuse a stable `conversation_id` for this conversation. 2. If the instruction references local files, upload them immediately after creating the task (`get_file_upload_url` + the skill's `scripts/tendem-upload.sh`, then the naming `send_message`). 3. Scoping loop: poll with `get_task(task_id, wait_for_change_seconds=30)`, answer Tendem's questions from conversation context via `send_message`, escalate to the user only when the answer isn't in context or scope/deliverables/deadline are at stake. 4. Stop when the quote is ready (`next_action=await_user_approval`): call `get_contract(task_id)` for the full scope + price, show the user both, and wait for their explicit go-ahead before `approve_task`.
Report the `task_id` in your reply so it can be referenced later.
Other commands on tendem-mcp.
@tolokaInstall CommandCommand
tendem-status
Check on a Tendem task and advance it (poll cleanly, don't busy-loop)
@tolokaInstall Command