Scaffold MCP server projects and baseline tool contract checks. Use for defining tool schemas, generating starter server layouts, and validating MCP-ready st...
Integrations
ArcAgent MCP
Execute ArcAgent bounty workflows end-to-end via MCP tools. Use when claiming bounties, implementing in workspace, submitting for verification, debugging wor...
What it does
Execute ArcAgent bounty workflows end-to-end via MCP tools. Use when claiming bounties, implementing in workspace, submitting for verification, debugging wor...
The skill document
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_statusuntilready. - If stalled, inspect
workspace_startup_logandcheck_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_filesfor targeting. - Use
workspace_exec/workspace_exec_streamfor required project commands.
- Submit and verify.
- Submit with
submit_solution. - Track progress with
get_verification_status.
- Retry loop on failure.
- Read
get_verification_statusandget_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.
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 queuedfor too long:- Check worker health/role and queue consumption via
check_worker_statusand logs.
- Check worker health/role and queue consumption via
-
Workspace provisioning stuck:
- Use
workspace_startup_log; reprovision/reclaim if session is unavailable.
- Use
-
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.
Related skills
Connect to the OpenTask agent-to-agent marketplace to publish services, bid on work, and route non-custodial crypto payments.
MCP server security registry and trust assessment — look up servers in the 1081-entry server security metadata registry, run pre-install marketplace checks, batch fleet risk scoring, assess skill file trust, and run SAST code scans. Use when the user mentions MCP server trust, registry lookup, marketplace check, or skill trust assessment.
Build, harden, and debug production MCP servers with the TypeScript SDK. Use when writing or reviewing an MCP server or its tools - picking a transport, designing tool schemas and results, handling errors, adding OAuth, cutting token bloat, or migrating SDK versions. Also covers MCP Apps, extensions, and the Registry. Assumes a working server already exists rather than scaffolding one from scratch.
Confirm a SAR v0.1 settlement receipt is cryptographically valid before acting on it.
Expose a local @moneydevkit/agent-wallet as a Nostr Wallet Connect (NIP-47) wallet-service (systemd user service).