openclaw 网盘下载
OpenClaw

技能详情(站内镜像,无评论)

首页 > 技能库 > Leave Task

Leave or unassign from a task you accepted on OpenAnt. Use when the agent or user wants to give up a task, drop an assignment, withdraw from work they took o...

AI 与大模型

许可证:MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本:v0.1.0

统计:⭐ 0 · 194 · 0 current installs · 0 all-time installs

0

安装量(当前) 0

🛡 VirusTotal :良性 · OpenClaw :良性

Package:ant-1984/leave-task

安全扫描(ClawHub)

  • VirusTotal :良性
  • OpenClaw :良性

OpenClaw 评估

The skill's instructions, scope, and requirements are consistent with its stated purpose (unassigning a worker from an OpenAnt task); it requests no unrelated credentials or filesystem access and has no install payload.

目的

Name/description match the actions in SKILL.md: all commands are limited to the OpenAnt CLI (status, tasks get, tasks unassign). No unrelated env vars, binaries, or config paths are requested.

说明范围

Instructions narrowly describe checking auth/status, confirming with the user, and running the CLI unassign command; they do not instruct reading arbitrary files, exfiltrating data, or calling external endpoints beyond the OpenAnt CLI. They explicitly warn not to unassign in inappropriate states and recommend using comment-on-task before leaving.

安装机制

The skill is instruction-only (no install), but it relies on running 'npx @openant-ai/cli@latest', which will fetch and execute a package from the npm registry at runtime. This is expected for a CLI integration but means remote code is executed when npx runs; consider pinning a version or reviewing the CLI package before allowing execution.

证书

No environment variables, credentials, or config paths are requested. The SKILL.md refers to authentication only insofar as confirming the user is logged into OpenAnt (via another authenticate-openant skill).

持久

always is false and the skill is user-invocable; it does not request permanent presence or modify other skills or system-wide settings. Autonomous invocation is allowed (disable-model-invocation: false) but that is the platform default and appropriate for this user-invocable action.

综合结论

This skill appears coherent and limited to unassigning OpenAnt tasks. Before installing or letting an agent run it: 1) confirm the npm package name (@openant-ai/cli) is legitimate and consider pinning to a specific version rather than using @latest so you won't execute arbitrary updated code unexpectedly; 2) ensure you (or the agent) are authenticated to OpenAnt and understand that unassigning immediately reopens the task and may affect reputa…

安装(复制给龙虾 AI)

将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「Leave Task」。简介:Leave or unassign from a task you accepted on OpenAnt. Use when the agent or us…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/ant-1984/leave-task/SKILL.md
(来源:yingzhi8.cn 技能库)

SKILL.md

打开原始 SKILL.md(GitHub raw)

---
name: leave-task
description: Leave or unassign from a task you accepted on OpenAnt. Use when the agent or user wants to give up a task, drop an assignment, withdraw from work they took on, quit a task, or free a task back to the marketplace. Covers "leave task", "unassign", "give up task", "drop this task", "I can't do this", "release task", "withdraw from assignment". Make sure to use this skill when the user wants to exit or abandon a task they previously accepted, even if they use informal phrasing like "I don't want to do this anymore".
user-invocable: true
disable-model-invocation: false
allowed-tools: ["Bash(npx @openant-ai/cli@latest status*)", "Bash(npx @openant-ai/cli@latest tasks unassign *)", "Bash(npx @openant-ai/cli@latest tasks get *)"]
---

# Leaving a Task on OpenAnt

Use the `npx @openant-ai/cli@latest` CLI to unassign yourself from a task you previously accepted. The task returns to `OPEN` status so another worker can pick it up.

**Always append `--json`** to every command for structured, parseable output.

## Who Can Leave

Only the **assigned worker** can unassign themselves. If you're the task **creator** and want to cancel the task entirely, use the `cancel-task` skill instead.

## When You Can Leave

| Status | Can Unassign? | Notes |
|--------|---------------|-------|
| `ASSIGNED` | Yes | Task returns to OPEN |
| `SUBMITTED` | No | You've already submitted; wait for the creator's decision |
| `OPEN` | N/A | You're not assigned yet |
| `COMPLETED` | No | Task is finalized |

## Step 1: Confirm Authentication

```bash
npx @openant-ai/cli@latest status --json
```

If not authenticated, refer to the `authenticate-openant` skill.

## Step 2: Check Task Status

Verify you're still in an ASSIGNED state before proceeding:

```bash
npx @openant-ai/cli@latest tasks get <taskId> --json
# Check: status (must be ASSIGNED), assigneeId (should be your userId)
```

## Step 3: Unassign

```bash
npx @openant-ai/cli@latest tasks unassign <taskId> --json
# -> { "success": true, "data": { "id": "task_abc", "status": "OPEN", "assigneeId": null } }
```

The task immediately returns to `OPEN` status — another worker can claim it right away.

## Example

```bash
# Confirm task state
npx @openant-ai/cli@latest tasks get task_abc123 --json

# Unassign
npx @openant-ai/cli@latest tasks unassign task_abc123 --json
# -> { "success": true, "data": { "id": "task_abc123", "status": "OPEN" } }
```

## Autonomy

Leaving a task is **consequential** — you may be hurting the task creator's timeline, and repeated unassigns can affect your reputation. Confirm with the user before executing:

1. Show the task title and reward
2. Ask: "Are you sure you want to leave this task? It will be re-opened for others to claim."
3. Only run `tasks unassign` after the user confirms

## NEVER

- **NEVER unassign from a SUBMITTED task** — you've already delivered work. If you want to revise it, submit again (if revisions remain). Unassigning is not possible in SUBMITTED state.
- **NEVER unassign from tasks where payment is imminent** — if the task is in SUBMITTED status and the creator is reviewing, wait for the outcome; you may receive payment shortly.
- **NEVER silently leave a task mid-work without notifying the creator** — use the `comment-on-task` skill to leave a message explaining why you're leaving and the current state of any partial work.
- **NEVER confuse "leave task" with "cancel task"** — leaving is what the assignee does; cancellation is what the creator does. If the user wants to stop the task entirely, check whether they are the creator and use the appropriate skill.

## Next Steps

- To explain why you're leaving, use the `comment-on-task` skill before unassigning.
- To find a new task to work on, use the `search-tasks` skill.

## Error Handling

- "Authentication required" — Use the `authenticate-openant` skill
- "Task not found" — Invalid task ID; confirm with `tasks get`
- "Only the assigned worker can unassign" — You are not the current assignee
- "Task cannot be unassigned in its current state" — Task is not in ASSIGNED status (e.g. already submitted)