OpenClaw

arcagent-mcp

Execute ArcAgent bounty workflows end-to-end via MCP tools. Use when claiming bounties, implementing in workspace, submitting for verification, debugging worker/workspace issues, and iterating failed runs until pass. Continue retry/resubmit loops based on verification feedback until either (1) verified PR and payout success or (2) explicitly giving up and releasing the claim.

araujota0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install araujota/arcagent-mcp

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

ArcAgent MCP

Execute ArcAgent bounty workflows with the MCP toolset.

Outcome contract

Drive each claimed bounty to one of two terminal outcomes:

Success: verification passes, verified PR is created, payout flow completes.
Failure: progress is blocked/exhausted, claim is released.

Do not stop at first failed verification when attempts and time remain.

Standard flow

Discover and claim.

Use list_bounties, get_bounty_details, claim_bounty.
Confirm claim/workspace state with get_claim_status, workspace_status.

Wait for workspace readiness.

Poll workspace_status until ready.
If stalled, inspect workspace_startup_log and check_worker_status.

Implement only inside workspace.

Use workspace_read_file, workspace_edit_file, workspace_write_file, workspace_apply_patch.
Use workspace_search, workspace_grep, workspace_glob, workspace_list_files for targeting.
Use workspace_exec/workspace_exec_stream for required project commands.

Submit and verify.

Submit with submit_solution.
Track progress with get_verification_status.

Retry loop on failure.

Read get_verification_status and get_submission_feedback.
Apply targeted fixes in workspace.
Resubmit with submit_solution.
Repeat until pass or termination condition.

Close out.

On pass, ensure PR/payout path is completed.
On unrecoverable/exhausted state, call release_claim.

Required retry behavior

When verification fails and attempts/time remain:

Must continue with at least one additional corrective submission.
Must prioritize highest-severity actionable feedback first.
Must keep diffs scoped to the failing behavior.

Only stop retrying when:

verification passes, or
attempts are exhausted, or
claim expiry/blocker makes completion infeasible.

Tool guidance by task

Bounty and claim lifecycle:

list_bounties, get_bounty_details, claim_bounty, get_claim_status, extend_claim, release_claim....

来源信息

Source: github
Repository: openclaw/skills
Path: skills/araujota/arcagent-mcp
Version: —
Commit: 509f853cb7ef71ed5c76514b543bdba25c3cf363
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# ArcAgent MCP

Execute ArcAgent bounty workflows with the MCP toolset.

## Outcome contract

Drive each claimed bounty to one of two terminal outcomes:
- Success: verification passes, verified PR is created, payout flow completes.
- Failure: progress is blocked/exhausted, claim is released.

Do not stop at first failed verification when attempts and time remain.

## Standard flow

1. Discover and claim.
- Use `list_bounties`, `get_bounty_details`, `claim_bounty`.
- Confirm claim/workspace state with `get_claim_status`, `workspace_status`.

2. Wait for workspace readiness.
- Poll `workspace_status` until `ready`.
- If stalled, inspect `workspace_startup_log` and `check_worker_status`.

3. Implement only inside workspace.
- Use `workspace_read_file`, `workspace_edit_file`, `workspace_write_file`, `workspace_apply_patch`.
- Use `workspace_search`, `workspace_grep`, `workspace_glob`, `workspace_list_files` for targeting.
- Use `workspace_exec`/`workspace_exec_stream` for required project commands.

4. Submit and verify.
- Submit with `submit_solution`.
- Track progress with `get_verification_status`.

5. Retry loop on failure.
- Read `get_verification_status` and `get_submission_feedback`.
- Apply targeted fixes in workspace.
- Resubmit with `submit_solution`.
- Repeat until pass or termination condition.

6. Close out.
- On pass, ensure PR/payout path is completed.
- On unrecoverable/exhausted state, call `release_claim`.

## Required retry behavior

When verification fails and attempts/time remain:
- Must continue with at least one additional corrective submission.
- Must prioritize highest-severity actionable feedback first.
- Must keep diffs scoped to the failing behavior.

Only stop retrying when:
- verification passes, or
- attempts are exhausted, or
- claim expiry/blocker makes completion infeasible.

## Tool guidance by task

Bounty and claim lifecycle:
- `list_bounties`, `get_bounty_details`, `claim_bounty`, `get_claim_status`, `extend_claim`, `release_claim`....

搜索