name: battle-claw description: Write code for free using your local GPU. Python, JS, TS, Go, PHP. 98% pass rate. version: 1.0.0 user-invocable: true metadata: {"clawdbot":{"requires":{"env":["ABCC_API_KEY"],"bins":["curl","bash"]},"primaryEnv":"ABCC_API_KEY","emoji":"⚔️","homepage":"https://github.com/mrdushidush/agent-battle-command-center"}}

Battle Claw

Route coding tasks through a local GPU for free instead of paying cloud API costs.

When to Activate

Use this skill when the user asks you to:

• Write a function, class, or module in Python, JavaScript, TypeScript, Go, or PHP
• Implement an algorithm or data structure
• Create a script, utility, or helper
• Generate any coding task that produces file output

When NOT to Activate

Do not use this skill when the user:

• Asks questions about existing code (answer directly)
• Requests file system operations or shell commands (do those yourself)
• Wants architecture discussions, planning, or code review (use normal chat)
• Needs non-code output (documentation, configs, diagrams)

Prerequisites

Before your first task, verify ABCC is running:

bash scripts/health.sh

If you see "status": "ready", proceed. If the health check fails, tell the user:

ABCC is not reachable at ${ABCC_API_URL:-http://localhost:3001}. Set it up with these commands:

mkdir agent-battle-command-center && cd agent-battle-command-center && mkdir -p scripts
curl -sLO https://raw.githubusercontent.com/mrdushidush/agent-battle-command-center/main/docker-compose.hub.yml
curl -sLO https://raw.githubusercontent.com/mrdushidush/agent-battle-command-center/main/.env.example
curl -sLo scripts/setup.sh https://raw.githubusercontent.com/mrdushidush/agent-battle-command-center/main/scripts/setup.sh
curl -sLo scripts/ollama-entrypoint.sh https://raw.githubusercontent.com/mrdushidush/agent-battle-command-center/main/scripts/ollama-entrypoint.sh
curl -sLo scripts/nginx-hub.conf https://raw.githubusercontent.com/mrdushidush/agent-battle-command-center/main/scripts/nginx-hub.conf
bash scripts/setup.sh
docker compose -f docker-compose.hub.yml up -d

Then set ABCC_API_KEY to the API_KEY value from the generated .env file.

Execution Steps

Step 1 — Determine Parameters

From the user's request, extract:

| Parameter | Required | Description | |-----------|----------|-------------| | description | Yes | What to build (use the user's words, 3-5000 chars) | | language | No | Default: python. One of: python, javascript, typescript, go, php | | file-name | No | Output filename (auto-generated if omitted) | | validation | No | Shell command to validate output (e.g., python -c "from task import fn; assert fn(2)==4") |

Step 2 — Execute the Task

Run the execute script:

bash scripts/execute.sh \
  --description "Create a Python function that reverses a string" \
  --language python

Or with all options:

bash scripts/execute.sh \
  --description "Implement an LRU cache with O(1) get and put" \
  --language python \
  --file-name lru_cache.py \
  --validation "python -c \"from lru_cache import LRUCache; c=LRUCache(2); c.put(1,1); assert c.get(1)==1\""

Alternatively, use curl directly:

curl -s --max-time 300 \
  -H "Content-Type: application/json" \
  -H "X-API-Key: ${ABCC_API_KEY}" \
  "${ABCC_API_URL:-http://localhost:3001}/api/battle-claw/execute" \
  -d '{"description":"Create a function that reverses a string","language":"python"}'

Step 3 — Parse the Response

The response is JSON on stdout. Key fields:

{
  "success": true,
  "taskId": "abc-123",
  "files": { "reverse_string.py": "def reverse_string(s: str) -> str:\n    return s[::-1]\n" },
  "validated": true,
  "complexity": { "score": 2, "source": "haiku" },
  "execution": { "model": "qwen2.5-coder:7b", "tier": "ollama", "timeMs": 11200 },
  "cost": { "actualCostUSD": 0, "cloudEquivalentUSD": 0.006, "savingsUSD": 0.006, "savingsPercent": 100 }
}

• If success is true: write each file from the files object to the user's workspace.
• If success is false: read the error field and tell the user what went wrong.

Step 4 — Write Files

For each entry in the files object, write the content to a file in the user's current working directory (or the path they specified) using the key as the filename.

Step 5 — Report Results

Tell the user:

1. What was created (filenames and a brief summary)
2. Complexity score and which model handled it
3. Cost savings (e.g., "Saved $0.006 vs cloud — this task was free")
4. If validated is true, mention the output was auto-validated

Stats Command

When the user asks about savings or statistics, run:

bash scripts/stats.sh

Report the key numbers: total tasks, success rate, total savings, and breakdown by language.

Troubleshooting

| Symptom | Cause | Fix | |---------|-------|-----| | connection refused | ABCC not running | Run docker compose up -d in the ABCC directory | | 401 Unauthorized | Bad or missing API key | Check ABCC_API_KEY is set correctly | | 503 Service Unavailable | Battle Claw service not initialized | Wait 10s for ABCC to finish starting up, then retry | | success: false with timeout | Task too complex or GPU overloaded | Check Ollama logs: docker logs abcc-ollama --tail 20 | | Empty files object | Agent wrote code but logs didn't capture it | Check the ABCC UI at http://localhost:5173 for the task |

External Endpoints

| Method | URL | Auth | Purpose | |--------|-----|------|---------| | POST | {ABCC_API_URL}/api/battle-claw/execute | X-API-Key: {ABCC_API_KEY} | Execute a coding task end-to-end | | GET | {ABCC_API_URL}/api/battle-claw/health | X-API-Key: {ABCC_API_KEY} | Check ABCC readiness and capabilities | | GET | {ABCC_API_URL}/api/battle-claw/stats | X-API-Key: {ABCC_API_KEY} | Cumulative task stats and savings |

ABCC_API_URL defaults to http://localhost:3001 if not set.

For full request/response schemas, see references/api-reference.md.

Security & Privacy

• Data locality: All code generation runs on your local GPU via Ollama. Only C10 decomposition tasks (~1% of requests) touch cloud APIs (Claude Sonnet).
• No telemetry: ABCC does not phone home or send usage data anywhere.
• API key scope: ABCC_API_KEY authenticates to your local ABCC instance only. It never leaves your machine.
• Network: The skill communicates only with localhost:3001 (or your configured ABCC_API_URL). No external network calls except for the rare cloud API task.
• File access: Generated code is returned in the HTTP response. The skill writes files only where you tell it to.