Claude Skills by boundless-xyz

github.com/boundless-xyz

15 skillsA× 10B× 3D× 1F× 10 installs19 views

Boundless CliAHow to use the Boundless CLI — the primary interface for the Boundless ZK proof marketplace. Covers requestor, prover, and rewards commands, config, env vars, and the monorepo structure. Use when working with the boundless CLI, submitting proofs, managing provers, staking rewards, or navigating the codebase.blockchainrustbashVotes: 0GitHub stars: 195
LocalnetAStart and interact with the Boundless localnet (docker compose-based local development network). Covers dev mode (fake proofs, broker included) and full proving mode, submitting requests, and debugging order flow. Use when the user wants to start localnet, run the local network, test proof requests locally, or debug broker/order-stream issues.blockchaingobashVotes: 0GitHub stars: 195
Ops Add New ChainAInternal — for Boundless team members only. Deploy Boundless infrastructure to a new blockchain. Creates Pulumi stacks, config files, updates ChainId enum, and wires CI/CD pipelines for staging and prod environments. Use when adding a new chain, deploying to a new network, or setting up new chain infrastructure.blockchaintypescriptgoVotes: 0GitHub stars: 195
Ops Check BalancesBInternal — for Boundless team members only. Audit native ETH, market deposit, prover collateral, and distributor ZKC reserve balances for every operator-managed address (provers, distributor, order generators, signal). Use when the user wants to know which addresses need topping up, asks about the balance of provers/OGs/distributor/signal signers, says something is "running low" or "out of gas", or wants a periodic operational health check on operator wallets. Defaults to prod env (mainnets +...blockchainpythongoVotes: 0GitHub stars: 195
Ops Indexer QueryAInternal — for Boundless team members only. Query the Boundless Indexer REST API for on-chain market data, staking, PoVW rewards, delegations, and market efficiency on prod/staging environments. Use when the user asks about proof requests, provers, requestors, staking data, PoVW rewards, delegations, market aggregates, leaderboards, or wants to fetch data from the indexer API on live networks. Also use when the user mentions "indexer" and wants to look up addresses, requests, or market statis...blockchaingoshellVotes: 0GitHub stars: 195
Ops Infra DeployFInternal — for Boundless team members only. Help developers deploy Boundless AWS infrastructure to the dev environment. Use when the user wants to deploy a service to dev, bootstrap their dev environment, troubleshoot infrastructure issues, or understand what env vars a service needs. Also handles teardown and status checks.blockchainshellbashVotes: 0GitHub stars: 195
Ops Logs QueryBInternal — for Boundless team members only. Query AWS CloudWatch logs for Boundless services (provers, slasher, distributor, order stream, order generator, indexer, signal) on prod/staging environments. Use when the user asks to look at service logs, debug service behavior from log output, search logs for a request ID, or investigate errors using CloudWatch. Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.blockchaingobashVotes: 0GitHub stars: 195
Ops PipelinesAInternal — for Boundless team members only. Monitor Boundless deployment pipelines (AWS CodePipeline + CodeBuild) on the ops account. Use when the user wants to track a deployment after merging a PR, check whether a commit has rolled out to staging/prod, diagnose a failed deployment, watch the status of a specific pipeline, or get prompted to approve a production rollout once staging succeeds. Do NOT use for service runtime debugging (use ops-logs-query) or for deploying dev infrastructure (u...blockchaingobashVotes: 0GitHub stars: 195
Ops QueryAInternal — for Boundless team members only. Cross-reference Boundless indexer API data, broker telemetry, and service logs to investigate production and staging operational issues. Use when the user wants to understand why slashings happened on prod/staging, diagnose prover or service failures in deployed environments, correlate market events with broker behavior, investigate fulfillment rate drops, look at prover/service logs, or perform any analysis that requires combining on-chain indexer ...blockchaingobashVotes: 0GitHub stars: 195
Ops Release NotesAInternal — for Boundless team members only. Generate release notes for a new Boundless version. Fetches PR details, explores code changes, and produces prover-facing documentation with config examples, migration guides, and worked examples. Use when the user wants to write release notes, changelog entries, or upgrade guides.blockchaingitdocumentationVotes: 0GitHub stars: 195
Ops Telemetry QueryAInternal — for Boundless team members only. Query Boundless broker telemetry tables on Redshift for prod/staging operational data. Use when the user asks about broker health, request evaluations, request completions, proving times, skip rates, telemetry data, or wants to run SQL against the telemetry database on live networks. Also covers historical telemetry through 2026-04-24 stored as Parquet archives in S3 (queried via DuckDB). Do NOT use for debugging local code changes, reviewing PRs, o...blockchainrustgoVotes: 0GitHub stars: 195
PrACreate or update a pull request for the current git changes. Use when the user wants a PR, commit/push for review, or gh pr create flow.blockchainrustgoVotes: 0GitHub stars: 195
RequestingDSubmit proof requests on the Boundless ZK proof marketplace. Covers wallet setup, CLI configuration, building or discovering guest programs, self-hosting via Cloudflare Quick Tunnels (no Pinata/S3 needed), submitting, and retrieving results. Use when a developer wants to request a ZK proof, submit a proof request, get started with Boundless, try Boundless, or learn the requestor workflow.blockchainpythonrustVotes: 0GitHub stars: 195
Setup ProverBSet up and deploy a Boundless prover to a GPU server using Ansible. Handles inventory setup, SSH connectivity, NVIDIA drivers, Docker, and the full bento stack. Use when deploying a new prover, redeploying to an existing server, or troubleshooting prover infrastructure.blockchainrustgoVotes: 0GitHub stars: 195
TestingAAfter completing non-trivial code changes, verify they are correct. Don't wait to be asked — if you made meaningful changes to Rust or Solidity code, run verification before reporting done. You can narrow test commands to just the crates/modules you changed (e.g. `cargo test -p broker --lib -- config::tests`), but follow the same patterns the justfile uses for flags and environment variables.blockchainrustgoVotes: 0GitHub stars: 195