القائمة
Run cli-wallet commands against a live Aztec network. Deploy contracts, send transactions, query state, bridge funds, and manage accounts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Spot-check the health of a live Aztec network deployment by sweeping recent GCP logs for warn/error messages, mapping each to the deployed code, classifying expected vs unexpected, and verifying the hard invariants (no slashing, no attestation timeouts, no unexplained prunes/conflicts). Use when asked to "spot-check", "review logs", or "health check" a network (staging, testnet, devnet, ...) over a recent window.
Reference for merge-train automation internals -- workflows, scripts, CI integration, and configuration. Use when modifying or debugging merge-train infrastructure.
Build and update the developer documentation site for a new release
Guide for working with merge-train branches -- creating PRs, choosing the right base branch, understanding labels, handling failures, and bypassing checks.
Create a well-formed Linear issue — with complete context for a fresh agent, a point estimate (1/2/3/5), and acceptance criteria. Works standalone or as part of planning a project with multiple issues. Use when asked to file/create/open a Linear issue, "make a ticket", or when breaking a plan into tracked work.
Build or adjust a Linear cycle — for a whole team or just yourself. Size capacity from last-3-cycle velocity, fill with backlog bugs/high-priority items first and project work after (in your chosen project focus order), with no unassigned issues. Use when planning/prepping a cycle for a team, or when one member wants to fill/rebalance their own cycle work.
| name | aztec-wallet |
| description | Run cli-wallet commands against a live Aztec network. Deploy contracts, send transactions, query state, bridge funds, and manage accounts. |
| argument-hint | <network-or-rpc-url> <command...> |
Run @aztec/cli-wallet commands against a live Aztec network. Handles network resolution, cli-wallet installation, account setup, and alias management automatically.
| Network | RPC Endpoint | Notes |
|---|---|---|
next-net | https://nextnet.aztec-labs.com | Runs nightly from next branch |
testnet | https://rpc.testnet.aztec-labs.com | Runs nightly from v4-next branch |
Custom RPC URLs (starting with http:// or https:// or IP addresses) are also accepted. If an IP address is provided without a port assume a default port of 8080.
Determine from the user's message:
0xc140de (schnorr account, salt 0)If the request is ambiguous, ask the user to clarify.
Do NOT run any bash commands (no curl, no version query). The agent handles that.
Spawn the aztec-wallet agent with a structured prompt:
FIRST: Read .claude/agents/aztec-wallet.md for full operational instructions.
Then execute the following:
NETWORK: <network-name or "custom">
RPC_URL: <resolved-url>
WORKING_DIR: /tmp/aztec-wallet-<network-name>/
PRIVATE_KEY: <hex, default 0xc140de>
SALT: 0
COMMAND: <what the user wants to do, in natural language or as a cli-wallet command>
The agent will query the node version, install the matching cli-wallet, set up the account, and execute the command.
IMPORTANT — shared WORKING_DIR: When spawning multiple agents (e.g. different accounts on the same network), they must ALL use the same WORKING_DIR (/tmp/aztec-wallet-<network-name>/). Do NOT create per-agent directories. Per-account isolation is already handled by INSTANCE_HASH inside the agent, which creates separate data_$INSTANCE_HASH subdirectories based on the private key and salt. Sharing the working dir also avoids redundant npm installs.
The cli-wallet has a persistent alias system. Use it consistently:
default for the auto-created account, or user-provided namesTokenContract → token)accounts:default, contracts:tokencontracts:token/aztec-wallet testnet status → show L2 address, balance, known contracts (no tx sent)/aztec-wallet testnet deploy TokenContract → deploy Token, alias as token/aztec-wallet testnet send mint_to_public on token --args <addr> 1000 → mint tokens/aztec-wallet testnet call balance_of_public on token --args <addr> → read balance/aztec-wallet testnet send mint_to_private on token --args <addr> 1000 → mint tokens to private balance/aztec-wallet testnet send transfer on token --args <recipient> 150 → private transfer (register recipient first)/aztec-wallet testnet bridge 1000 to <address> → bridge Fee Juice (requires Sepolia ETH on L1)/aztec-wallet next-net setup-account → create account, show L2 address for bridging/aztec-wallet https://my-rpc.com deploy ./path/to/artifact.json → custom RPC + custom contractregister-sender <recipient-address> before sending private tokensbridge-fee-juice requires Sepolia ETH on the L1 address — it won't work with an unfunded key