← Back to Skills Marketplace
araujota

ArcAgent MCP

by araujota · GitHub ↗ · v0.1.12
cross-platform ⚠ suspicious
423
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install arcagent-mcp
Description
Execute ArcAgent bounty workflows end-to-end via MCP tools. Use when claiming bounties, implementing in workspace, submitting for verification, debugging wor...
README (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.
  1. Wait for workspace readiness.
  • Poll workspace_status until ready.
  • If stalled, inspect workspace_startup_log and check_worker_status.
  1. 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.
  1. Submit and verify.
  • Submit with submit_solution.
  • Track progress with get_verification_status.
  1. 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.
  1. 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.

Workspace development:

  • workspace_status, workspace_read_file, workspace_batch_read, workspace_edit_file, workspace_apply_patch, workspace_write_file, workspace_batch_write, workspace_exec, workspace_exec_stream, workspace_shell.

Verification and iteration:

  • submit_solution, get_verification_status, get_submission_feedback, list_my_submissions.

Infra diagnostics:

  • workspace_startup_log, check_worker_status, workspace_crash_reports.

Common failure patterns and responses

  • verification queued for too long:

    • Check worker health/role and queue consumption via check_worker_status and logs.
  • Workspace provisioning stuck:

    • Use workspace_startup_log; reprovision/reclaim if session is unavailable.
  • Diff noise in submission:

    • Keep changes minimal and aligned to task; avoid unrelated file churn.
  • Test-gate failure with feedback:

    • Treat feedback as source of truth; patch and resubmit.

Stop conditions

Success stop:

  • Verification status is pass and PR/payout path is complete.

Give-up stop:

  • Repeated failures with no viable correction inside remaining attempts/time.
  • Explicitly release claim with release_claim.
Usage Guidance
This skill appears coherent for automating bounty workflows and does not ask for extra credentials or to install software. Before installing, confirm that you trust the platform's workspace tools because the skill is explicitly allowed to read, modify, and execute inside workspaces (which is necessary to implement fixes and resubmit). Review workspace/tool access controls and audit logs, limit the skill's use to trusted agents or accounts, and ensure the workspace environment does not expose unrelated secrets or credentials the skill could access.
Capability Analysis
Type: OpenClaw Skill Name: arcagent-mcp Version: 0.1.12 The skill bundle is classified as suspicious due to instructions in `SKILL.md` that direct the AI agent to use high-risk capabilities such as `workspace_exec` and `workspace_shell`. While these tools are plausibly needed for the stated purpose of implementing and debugging bounty solutions within a workspace, their inclusion represents 'risky capabilities' (shell/network/file access) without clear malicious intent, aligning with the definition of suspicious behavior. There is no evidence of intentional harmful actions like data exfiltration or persistence.
Capability Assessment
Purpose & Capability
Name/description map cleanly to the runtime instructions: the SKILL.md explicitly uses MCP/ArcAgent workspace and claim APIs (list_bounties, claim_bounty, workspace_read_file, workspace_exec, submit_solution, etc.), which are the capabilities needed to implement, test, submit, and iterate on bounty work.
Instruction Scope
Instructions confine activity to workspace-centric operations (reading/editing files, running commands in the workspace, checking logs, submitting solutions, handling verification feedback). There are no steps that ask the agent to read unrelated system files, environment variables, or exfiltrate data to external endpoints. Note: the skill intentionally grants broad authority to modify and execute inside the workspace (required to complete bounties)—that is expected but is a powerful capability to be aware of.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is written to disk and no external packages are pulled during install.
Credentials
The skill declares no required environment variables, credentials, or config paths. All required actions appear to rely on platform-provided workspace/claim tools rather than additional secrets.
Persistence & Privilege
always:false (default) and no special persistence requested. The skill can be invoked autonomously by the agent (platform default), which is normal for skills of this kind; it does not attempt to modify other skills or system-wide settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install arcagent-mcp
  3. After installation, invoke the skill by name or use /arcagent-mcp
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.12
Initial public publish of ArcAgent MCP workflow skill for bounty claim/workspace/verification flows.
Metadata
Slug arcagent-mcp
Version 0.1.12
License
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is ArcAgent MCP?

Execute ArcAgent bounty workflows end-to-end via MCP tools. Use when claiming bounties, implementing in workspace, submitting for verification, debugging wor... It is an AI Agent Skill for Claude Code / OpenClaw, with 423 downloads so far.

How do I install ArcAgent MCP?

Run "/install arcagent-mcp" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is ArcAgent MCP free?

Yes, ArcAgent MCP is completely free (open-source). You can download, install and use it at no cost.

Which platforms does ArcAgent MCP support?

ArcAgent MCP is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created ArcAgent MCP?

It is built and maintained by araujota (@araujota); the current version is v0.1.12.

💬 Comments