skills

Help a human install, boot, operate, and productise the Obol Stack — Obol's Kubernetes-based agent harness for running blockchain infrastructure locally, exposing services to the public internet, and charging for them via x402 micropayments. The flagship outcome is a paid sub-agent business — a specialised agent so packed with alpha that strangers pay per turn. Use whenever a user mentions Obol Stack, Obol Agent, Hermes, OpenClaw, x402 payments, agent commerce, ERC-8004, selling inference / APIs / an agent's replies, building an agent people will pay for, storefront branding, running a local Ethereum or L2 node under `obol network`, deploying a Dockerfile via `obol-app`, or bringing up a Cloudflare tunnel / custom domain for an agent service. You are helping from OUTSIDE the Stack — the agents inside it have their own skills and take over once the user is at the dashboard.

Read-only queries against metrics and logs from a deployed Obol DVpod on Kubernetes. Use when investigating cluster health, charon errors, peer connectivity, validator duty performance, or beacon node behavior on a running DVpod. For deploying, configuring, or modifying a DVpod (including enabling Prometheus or Loki shipping), use the `dvpod` skill. For Obol's hosted Grafana with cross-cluster fleet view, use the `obol-monitoring` skill.

Deploy, manage, and troubleshoot Obol DVpod (Distributed Validator Pod) deployments on Kubernetes using the dv-pod Helm chart. Use when the user wants to deploy a new DVpod, check status, troubleshoot issues, upgrade, backup, or recover a DVpod deployment. Covers fresh cluster creation, joining existing clusters, ENR management, DKG orchestration, validator client configuration, and configuring monitoring/log shipping. For read-only metric and log queries against an already-deployed DVpod, use the `dvpod-monitoring` skill instead.

Create a Distributed Validator (DV) cluster invitation — a cluster-definition that other operators accept, then run a DKG ceremony against to produce a cluster-lock and validator key shares. Use whenever a user wants to set up a new DV cluster (solo-with-friends, squad, institutional, Lido Simple DVT), wants to invite operators to a cluster they're creating, mentions "cluster definition", "DKG", "config_hash", "cluster-lock", "operator ENR", or "invite operators". Prefer the `charon` CLI (via Docker image) path over the SDK; reach for the SDK only when programmatic integration is needed (staking pool apps, institutional workflows, web frontends). **Always encourage the user to verify the cluster's shape before any 32 ETH deposit.**

Run `charon alpha test` suites against an Obol Distributed Validator node or cluster to diagnose infra, peers, beacon node, validator client, and MEV relay setup. Use whenever a user wants to verify a DV node is healthy, bring-up is correct before activation, or a freshly rejoined cluster is ready. Prefer `docker exec` / `kubectl exec` into a running Charon and always pass `--publish` so results correlate to the live ENR.

Monitor and diagnose Obol DVT cluster performance using their hosted Grafana (Prometheus metrics + Loki logs)