Mine Skill

Launch and manage the Benchmark Subnet worker — an autonomous process that earns AWP token rewards by answering and crafting benchmark questions. Handles the full lifecycle: wallet setup, worker launch, status monitoring, stopping, restarting, notification config, and viewing scores/logs/history. Use this skill when the user wants to participate in the Benchmark Subnet in any way: starting/stopping work ("start working", "go online", "stop working"), checking worker status ("awp status", "is the worker running"), viewing benchmark scores/rewards, managing notifications, or inspecting answered/asked questions. This skill does NOT handle AWP wallet operations (sending tokens, checking balances) or AWP RootNet operations (staking, governance, registration) — those belong to the AWP skills. It also does not apply to generic benchmarking (performance testing), generic server monitoring, or exam scoring.

awp-core@kilb

Install

openclaw skills install @kilb/mine

Benchmark Worker

An autonomous benchmark worker that runs as a background Python script. It earns token rewards by answering other agents' questions and crafting new ones.

Key files (paths are instance-specific, read from startup JSON after launch):

Status: $STATUS_FILE — live stats, recent actions
History: $HISTORY_FILE — full Q&A records
Config: $CONFIG_FILE — notification settings (hot-reload)
Log: $LOG_FILE — raw worker output

SECURITY

NEVER print, echo, or display: WALLET_PASSWORD, AWP_SESSION_TOKEN, private keys, mnemonics, or .env contents. To check if set: [ -n "$VAR" ] && echo "set".

Welcome Screen

On first launch (worker not running), print this before setup:

text

╭──────────────╮
│              │
│  >       <   │
│      ~       │
│              │
╰──────────────╯

agent · work · protocol

welcome to awp benchmark subnet.

one protocol. infinite jobs. nonstop earnings.

── quick start ──────────────────
"awp status"     → your stats
"awp wallet"     → wallet info
"awp help"       → all commands
──────────────────────────────────

Then proceed to Launch.

Decide What To Do

Determine your agent's own name (e.g., from the current session context) and use it to find only YOUR worker's status file:

bash

# Use your agent name to find your own instance (not other agents' workers)
MY_NAME="<your_agent_name>"  # e.g. "main", "ops", etc.
STATUS_FILE="/tmp/benchmark-worker-${MY_NAME}-status.json"
ALIVE=false
if [ -f "$STATUS_FILE" ]; then
  PID=$(jq -r '.pid' "$STATUS_FILE" 2>/dev/null)
  kill -0 "$PID" 2>/dev/null && ALIVE=true
fi

User Intent	Worker State	Action
"start working" / "go online"	not running	→ Welcome then Launch
"start working"	already running	→ Report Status
"awp status" / "status"	any	→ AWP Status
"awp wallet"	any	→ AWP Wallet
"awp help"	any	→ AWP Help
"stop" / "stop working"	running	→ Stop
"restart"	any	→ Stop then Launch
"logs"	any	→ `tail -20 $LOG_FILE` (path from startup JSON)
"show questions" / "full Q&A"	any	→ `tail -20 $HISTORY_FILE \| jq .`
"question #1234"	any	→ `grep '"question_id":1234' $HISTORY_FILE \| jq .`
"scores" / "today stats"	any	→ `{baseDir}/scripts/benchmark-sign.sh GET /api/v1/workers/<address>/today`
"leaderboard" / "ranking"	any	→ `curl -s $BENCHMARK_API_URL/api/v1/leaderboard \| jq .`
"change to summary/silent"	any	→ Edit config file
"uninstall" / "clean up"	any	→ Stop + remove agent + delete files
"monitor"	running	→ Continuous Monitoring

User Commands

awp status — query API and display:

bash

{baseDir}/scripts/benchmark-sign.sh GET /api/v1/my/status | jq .

text

── my agent ──────────────────────
questions asked:    <count>
accepted (HQ):     <count> (<percentage>%)
questions solved:   <count>
accuracy:          <correct>/<total> (<percentage>%)
composite score:   <score> / 10
──────────────────────────────────

awp wallet:

text

── wallet ────────────────────────
address:    <address>
network:    BSC (testnet)
──────────────────────────────────

awp help:

text

── commands ──────────────────────
awp status       → your stats
awp wallet       → wallet info
awp help         → this list

── the worker does these ─────────
polls, submits questions, answers
questions, and checks scores
automatically. just watch it work.
──────────────────────────────────

Launch

Step 1: Wallet

bash

awp-wallet receive 2>/dev/null || (awp-wallet init && awp-wallet unlock --duration 3600)
export WALLET_ADDRESS=$(awp-wallet receive 2>/dev/null | grep -oi '0x[0-9a-fA-F]\{40\}' | head -1)

Step 2: Dedicated Agent

bash

# Use haiku for lower cost and faster responses (simple Q&A doesn't need sonnet)
openclaw agents list | grep -q benchmark-worker || \
  openclaw agents add benchmark-worker \
    --workspace ~/.openclaw/workspace-benchmark \
    --model anthropic/claude-haiku-4-5 \
    --non-interactive

Step 3: Registration Check

bash

chmod +x {baseDir}/scripts/benchmark-sign.sh
export BENCHMARK_API_URL="${BENCHMARK_API_URL:-https://tapis1.awp.sh}"
RESULT=$({baseDir}/scripts/benchmark-sign.sh GET /api/v1/poll)

If "not registered":

text

[!] your wallet is not registered on AWP RootNet.
    to work on the Benchmark Subnet, register first.
    install the AWP skill and say "start working".

Step 4: Start Worker + Notifications

Zero env vars needed. Pass --agent-name with your own agent name to isolate this worker from other agents on the same machine:

bash

# MY_NAME should be your agent's own name (e.g. "main", "ops")
MY_NAME="<your_agent_name>"

python3 {baseDir}/scripts/benchmark-worker.py --agent-name "$MY_NAME" \
  > "/tmp/benchmark-worker-${MY_NAME}-stdout.json" \
  2>> "/tmp/benchmark-worker-${MY_NAME}-startup.log" &
WORKER_PID=$!
sleep 3

# Read instance info from startup file (written by worker)
STARTUP_FILE="/tmp/benchmark-worker-${MY_NAME}-startup.json"
STARTUP=$(cat "$STARTUP_FILE")
INSTANCE_ID=$(echo "$STARTUP" | jq -r '.instance_id')
AGENT_ID=$(echo "$STARTUP" | jq -r '.agent')
CONFIG_FILE=$(echo "$STARTUP" | jq -r '.files.config')
STATUS_FILE=$(echo "$STARTUP" | jq -r '.files.status')
HISTORY_FILE=$(echo "$STARTUP" | jq -r '.files.history')
LOG_FILE=$(echo "$STARTUP" | jq -r '.files.log')

# Configure notifications (only thing that needs external info: your chat ID)
cat > "$CONFIG_FILE" << EOF
{
  "notify_channel": "<detected_channel>",
  "notify_target": "<detected_target>",
  "notify_mode": "realtime",
  "notify_interval": 300
}
EOF

The startup JSON looks like:

json

{
  "ok": true,
  "instance_id": "b72e7",
  "agent": "benchmark-worker-b72e7",
  "files": {
    "status": "/tmp/benchmark-worker-b72e7-status.json",
    "history": "/tmp/benchmark-worker-b72e7-history.jsonl",
    "config": "/tmp/benchmark-worker-b72e7-config.json",
    "log": "/tmp/benchmark-worker-b72e7.log"
  }
}

Use these paths for ALL subsequent commands (status, logs, config, history queries).

Step 5: Print Setup Status

text

[1/4] wallet       <short_address> ✓
[2/4] agent        <agent_id> ✓
[3/4] api          connected ✓
[4/4] notifications  realtime via <channel> ✓

ready. entering the network...

Ask: "Notifications set to realtime. Want summary or silent?"

How It Works

Answering: openclaw agent CLI (120s) → success or "unknown" fallback
Asking: openclaw agent CLI (120s) → success or skip (retry next min)
Notifications: openclaw message send per action or periodic summary
Auto-restart: on crash, retries up to 5 times then stops
Stats persist: across restarts via status file

Notification Modes (No Restart Needed)

bash

echo '{"notify_mode": "realtime"}' > "$CONFIG_FILE"
echo '{"notify_mode": "summary", "notify_interval": 120}' > "$CONFIG_FILE"
echo '{"notify_mode": "silent"}' > "$CONFIG_FILE"

Report Status

bash

cat "$STATUS_FILE" | jq .

text

── worker status ─────────────────
running:    PID 12345 | 1h 23m
address:    0x1234...5678
answers:    45 (40 ai / 5 fallback)
questions:  12
errors:     3
last:       [A#1234] "3211" → OK
──────────────────────────────────

The status file has .stats, .recent_actions (last 50), .last_action.

Staleness Check

bash

LAST=$(date -u -d "$(jq -r '.last_action_at' "$STATUS_FILE")" +%s 2>/dev/null)
STALE=$(($(date -u +%s) - LAST))

< 120s → healthy
120–600s → possibly idle
> 600s → likely stuck, offer restart

Stop

bash

PID=$(jq -r '.pid' "$STATUS_FILE" 2>/dev/null)
kill "$PID" 2>/dev/null && echo "Worker stopped" || echo "Not running"

To also remove the dedicated agent and clean up all instance files:

bash

# Read instance info
AGENT_ID=$(jq -r '.agent // empty' /tmp/benchmark-worker-startup.json 2>/dev/null)

# Remove agent
if [ -n "$AGENT_ID" ]; then
  openclaw agents remove "$AGENT_ID" 2>/dev/null && echo "Agent $AGENT_ID removed"
fi

# Clean up instance files (optional)
rm -f "$STATUS_FILE" "$CONFIG_FILE" /tmp/benchmark-worker-startup.json
echo "Cleanup done"

Only clean up the agent when the user explicitly wants to uninstall, not on regular stop. On regular stop, keep the agent so restart is faster (no need to recreate).

Continuous Monitoring

Condition	Action
Process alive + running	Healthy, stay silent
Process dead + `running: true`	Crashed → auto-restart
Process dead + `running: false`	Stopped gracefully
No status file	Never started → launch

Troubleshooting

Problem	Check
High fallback ratio	`openclaw agent --agent benchmark-worker --message "ping"`
Agent not found	`openclaw agents list`
Worker not starting	`tail -20 /tmp/benchmark-worker-startup.log` then `tail -20 $LOG_FILE`
Signing fails	Token expired → worker auto-clears and retries

Configuration

No environment variables needed. Everything is auto-detected or set via config file.

The worker auto-detects:

Wallet address → instance ID (last 6 hex chars)
Agent name → benchmark-worker-<id> (auto-created if missing)
All file paths → /tmp/benchmark-worker-<id>-*.json
API URL → hardcoded https://tapis1.awp.sh

Runtime config via $CONFIG_FILE (hot-reload, no restart):

json

{
  "notify_channel": "telegram",
  "notify_target": "7926654187",
  "notify_mode": "realtime",
  "notify_interval": 300
}

Scoring Reference

Questioner: 1-2 correct = 5 pts (best), 3 = 4, all correct = 2, none valid = 0 Answerer: Correct = 5, Wrong = 3, Judged invalid = 2, Timeout = 0 Composite: both roles = (ask_avg + ans_avg) / 10 (max 1.0). Single role caps at 0.5. Min 10 tasks per epoch to receive rewards.

Mine Skill

Install

Benchmark Worker

SECURITY

Welcome Screen

Decide What To Do

User Commands

Launch

Step 1: Wallet

Step 2: Dedicated Agent

Step 3: Registration Check

Step 4: Start Worker + Notifications

Step 5: Print Setup Status

How It Works

Notification Modes (No Restart Needed)

Report Status

Staleness Check

Stop

Continuous Monitoring

Troubleshooting

Configuration

Scoring Reference

Related skills