ワンクリックで
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Review a task that has been offered to you and decide whether to accept or reject it
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use swarm scripts for bulk SDK calls, repetitive fan-out, and context-efficient data processing.
Fetch a file attached to your current task in ONE call. Use whenever a task carries an attachment (an image, PDF, or other file the requester uploaded) and you need its bytes on disk — the dispatch prompt lists attachments with a ready-to-run curl command, but if you're improvising (resumed session, follow-up task, or the recipe scrolled out of context) use this skill instead of reaching for the `agent-fs` CLI directly.
Guide for running local E2E tests with API server, Docker lead/worker containers, task creation, log verification, UI dashboard, and cleanup
Canonical AgentMail send-message API reference for swarm agents. Pins the base URL, required field names, text-only rendering workaround, BCC policy, and ready-to-copy curl / swarm-script examples so agents do not rediscover the API surface at runtime.
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and resolve contacts to swarm users. Canonical reference for ANY Kapso interaction beyond the thin `send-whatsapp-message` / `reply-whatsapp-message` MCP tools — for templates, media, reactions, typing, mark-as-read, signature verify, contact resolution, conversation history, drop to the REST recipes here. Use whenever a task references a WhatsApp message routed through Kapso, or when a workflow needs to reply on WhatsApp.
Per-app playbook for driving Gmail through Composio (toolkit slug `gmail`). Verified GMAIL_* tool slugs and argument shapes for reading, searching, sending, drafts, labels, and threads. Use alongside the `composio` hub skill whenever a task reads or sends Gmail for a connected user. Covers the metadata-first reads, the GMAIL_SEND_EMAIL HTML flag, and reply-to-thread.
| name | review-offered-task |
| description | Review a task that has been offered to you and decide whether to accept or reject it |
You have been offered a task. Your job is to review it and decide whether to accept or reject it based on your capabilities and current workload.
Get task details: Call the get-task-details tool with the provided taskId to understand what the task involves.
Evaluate the task: Consider:
Make a decision:
task-action with action: "accept" and taskId: "<taskId>". Then immediately use /skill:work-on-task <taskId> to start working on it.task-action with action: "reject", taskId: "<taskId>", and provide a reason explaining why you're rejecting it (e.g., "Task requires Python expertise which I don't have", "Task description is too vague").1. get-task-details taskId="abc-123"
2. [Review the task details]
3. task-action action="accept" taskId="abc-123"
4. /skill:work-on-task abc-123
1. get-task-details taskId="abc-123"
2. [Review the task details]
3. task-action action="reject" taskId="abc-123" reason="Task requires access to production database which I don't have"
4. Reply "DONE" to end the session
/skill:work-on-task