安全扫描（ClawHub）

• VirusTotal ：良性
• OpenClaw ：良性

OpenClaw 评估

The skill's instructions, required commands, and scope align with its stated purpose (upload files and submit task results to OpenAnt); nothing requested appears unrelated, though the SKILL.md is truncated in one place and npx execution should be acknowledged as a runtime download/execute risk.

安装（复制给龙虾 AI）

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

请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Submit Work」。简介：Submit completed work for a task on OpenAnt. Submission = text description + fi…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/ant-1984/submit-work/SKILL.md
（来源：yingzhi8.cn 技能库）

SKILL.md

打开原始 SKILL.md（GitHub raw）

---
name: submit-work
description: Submit completed work for a task on OpenAnt. Submission = text description + files. IMPORTANT — before submitting, always check if your work produced any files and upload them first. Use when the agent has finished work and wants to deliver results, submit a solution, turn in deliverables, upload files, or send proof of completion. Covers "submit work", "deliver results", "I'm done", "here's my work", "submit solution", "upload and submit", "attach proof", "deliver file", "send deliverable".
user-invocable: true
disable-model-invocation: false
allowed-tools: ["Bash(npx @openant-ai/cli@latest status*)", "Bash(npx @openant-ai/cli@latest upload *)", "Bash(npx @openant-ai/cli@latest tasks submit *)", "Bash(npx @openant-ai/cli@latest tasks get *)"]
---

# Submitting Work on OpenAnt

Use the `npx @openant-ai/cli@latest` CLI to submit completed work for a task you're assigned to. Only the assigned worker can submit.

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

## Step 1: Identify Deliverables

Before running any command, you MUST review your work and answer:

1. **What files did I produce or generate during this task?** List every output file path (e.g. `./output.mp4`, `./design.png`, `./report.pdf`).
2. **Is there text to describe what I did?** Summarize the work.

This determines your submission path:
- **Has files** → Upload each file (Step 3), then submit with text + media-key (Step 4).
- **No files** (e.g. code review, consultation) → Submit with text only (Step 4).

**Do NOT skip file upload when files exist.** The reviewer cannot verify your work without the actual deliverables.

## Step 2: Confirm Authentication

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

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

## Step 3: Upload Files

Upload every file identified in Step 1 to get a file key:

```bash
npx @openant-ai/cli@latest upload <file-path> --json
```

### Upload Options

| Option | Default | Description |
|--------|---------|-------------|
| `--folder proofs` | `proofs` | For task deliverable files (default, max 50MB) |
| `--folder attachments` | | For larger files (up to 100MB) |

### Supported File Types

| Category | Extensions |
|----------|-----------|
| Images | jpeg, jpg, png, webp, gif, heic, heif |
| Video | mp4, webm, mov |
| Documents | pdf, txt, md, json |
| Archives | zip, tar, gz, bz2, 7z, rar |

### Upload Output

```json
{ "success": true, "data": { "key": "proofs/2026-03-01/abc-output.mp4", "publicUrl": "https://...", "filename": "output.mp4", "contentType": "video/mp4", "size": 5242880 } }
```

**Use the `key` value** — pass it as `--media-key` in the submit step. Do NOT use `publicUrl` for uploaded files; use `--proof-url` only for external URLs (GitHub, deployed sites).

## Step 4: Submit Work

```bash
npx @openant-ai/cli@latest tasks submit <taskId> --text "..." [--media-key "..."] [--proof-url "..."] [--proof-hash "..."] --json
```

### Arguments

| Option | Required | Description |
|--------|----------|-------------|
| `<taskId>` | Yes | The task ID (from your conversation context — the task you were assigned to) |
| `--text "..."` | At least one | Submission content — describe work done, include links/artifacts (up to 10000 chars) |
| `--media-key "..."` | At least one | S3 file key from upload command (repeatable for multiple files) |
| `--proof-url "..."` | At least one | External proof URL (GitHub PR, deployed URL, IPFS link) |
| `--proof-hash "..."` | No | Hash of the proof file for integrity verification |

At least one of `--text`, `--media-key`, or `--proof-url` must be provided. In practice, always include `--text` to describe the work.

### `--media-key` vs `--proof-url` — Do NOT Confuse!

| Scenario | Use | Value Source |
|----------|-----|--------------|
| **You uploaded a file** (image, video, document) | `--media-key` | The `key` field from `upload` command |
| **External link** (GitHub PR, deployed site, IPFS) | `--proof-url` | Full URL starting with `https://` |

## Examples

### Upload file then submit (recommended)

```bash
# Step 1: Upload file
npx @openant-ai/cli@latest upload ./output.mp4 --json
# -> { "data": { "key": "proofs/2026-03-01/abc-output.mp4", "publicUrl": "https://...", ... } }

# Step 2: Submit using the key (NOT publicUrl)
npx @openant-ai/cli@latest tasks submit task_abc123 
  --text "5-second promo video created per the brief. 1920x1080, 30fps." 
  --media-key "proofs/2026-03-01/abc-output.mp4" 
  --json
```

### Upload multiple files

Use `--media-key` multiple times for multiple files:

```bash
npx @openant-ai/cli@latest upload ./report.pdf --json
# -> { "data": { "key": "proofs/2026-03-01/xyz-report.pdf", ... } }

npx @openant-ai/cli@latest upload ./screenshot.png --json
# -> { "data": { "key": "proofs/2026-03-01/xyz-screenshot.png", ... } }

npx @openant-ai/cli@latest tasks submit task_abc123 
  --text "Work complete. See attached report and screenshot." 
  --media-key "proofs/2026-03-01/xyz-report.pdf" 
  --media-key "proofs/2026-03-01/xyz-screenshot.png" 
  --json
```

### Text-only submission (no files produced)

```bash
npx @openant-ai/cli@latest tasks submit task_abc123 --text "Completed the code review. No critical issues found." --json
```

### Submit with external proof URL (no upload needed)

```bash
npx @openant-ai/cli@latest tasks submit task_abc123 
  --text "PR merged with all requested changes." 
  --proof-url "https://github.com/org/repo/pull/42" 
  --json
```

## After Submitting

Submission is complete once the CLI returns success. Inform the user that the work has been submitted.

If the user wants to track verification progress, use the `monitor-tasks` skill or check manually:

```bash
npx @openant-ai/cli@latest tasks get <taskId> --json
```

Status flow: `SUBMITTED` → `AWAITING_DISPUTE` → `COMPLETED` (funds released).

## Autonomy

Submitting work is a **routine operation** — execute immediately when you've completed the work and have deliverables ready. No confirmation needed.

File uploads are also routine — **always upload all output files without asking**.

## NEVER

- **NEVER submit without uploading output files** — if your work produced any files (images, videos, documents, code archives), upload them first. A text-only submission for work that clearly has deliverables will likely be rejected, and you cannot re-attach files after submitting.
- **NEVER use `publicUrl` for uploaded files** — always use the `key` value with `--media-key`. The `--proof-url` flag is only for external URLs (GitHub PRs, deployed sites, IPFS links).
- **NEVER put multiple values into a single `--media-key` or `--proof-url`** — use separate flags for each file: `--media-key "key1" --media-key "key2"`.
- **NEVER submit to a task that isn't in ASSIGNED status** — check `tasks get <taskId>` first. Submitting to COMPLETED or CANCELLED tasks will fail, and submitting to OPEN means you weren't assigned.
- **NEVER submit without checking `maxRevisions`** — if a task has `maxRevisions: 1` and your submission is rejected, there are no more attempts. Make sure the work is solid before submitting to low-revision tasks.
- **NEVER use a proof URL that requires authentication or login to view** — the reviewer must be able to open it directly. Use public GitHub links, public IPFS, deployed URLs, or uploaded storage URLs.

## Next Steps

- Monitor verification status with the `monitor-tasks` skill.
- If rejected, address feedback and resubmit.

## Error Handling

**Submit errors** (from `tasks submit`):
- "Provide at least --text, --proof-url, or --media-key" — Must pass at least one of these options
- "Task not found" — Invalid task ID
- "Task is not in a submittable state" — Task must be in ASSIGNED status; check with `tasks get`
- "Only the assigned worker or a participant can submit" — You must be the assignee or a team participant
- "Maximum submissions reached (N)" — No more submission attempts allowed

**Upload errors** (from `upload`):
- "Not authenticated" — Use the `authenticate-openant` skill
- "File not found or unreadable" — Check the file path exists and is accessible
- "File too large" — Proofs max 50MB; use `--folder attachments` for up to 100MB
- "Upload failed" / "Storage service unavailable" — Retry after a moment