Skill
tendem-result
Explicitly fetch and present a completed Tendem task's result (markdown + files). Invoke as $tendem-result [task_id] — omit the…
@tolokaInstall SkillSales
Skill
/tendem-status
Explicitly check on a Tendem task and advance it (poll cleanly, don't busy-loop). Invoke as $tendem-status [task_id] — omit the task_id to pick from recent tasks.
Install
$ npx -y skills add toloka/tendem-mcp --skill tendem-status --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/tendem-status
Context preview
The summary Claude sees to decide when to auto-load this skill.
Explicitly check on a Tendem task and advance it (poll cleanly, don't busy-loop). Invoke as $tendem-status [task_id] — omit the task_id to pick from recent tasks.
SKILL.md
tendem-status.SKILL.mdname: tendem-status description: Explicitly check on a Tendem task and advance it (poll cleanly, don't busy-loop). Invoke as $tendem-status [task_id] — omit the task_id to pick from recent tasks.
Check the status of a Tendem task and take the next correct step.
- If a `task_id` accompanies this invocation, 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. The task lives on Tendem's side, nothing is lost between sessions — the user can simply ask again later ("how's the Tendem task doing?" or `$tendem-status`), and the plugin's notification hook pings them the moment the task needs them.
- `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` → follow the `tendem-result` skill (or call `get_task_result`).
- `done` → nothing left; summarize the outcome.
Summarize where the task stands and what happens next in plain language.
Other skills on tendem-mcp.
@tolokaInstall SkillSkill
tendem-task
Explicitly submit a new task to Tendem (hybrid AI + human experts) and drive it through scoping. Invoke as $tendem-task <what you…
@tolokaInstall SkillSkill
tendem-tasks
Use when a task is non-trivial and could benefit from human involvement — delegating work to a human expert (research, review,…
@tolokaInstall Skill