aztec-wallet

Execute Aztec wallet CLI workflows from natural-language blockchain intents.

Updated May 14, 2026
One-click install
npx skills add https://github.com/HabibTorjmen/Blockchain --skill aztec-wallet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aztec-wallet
Source: https://github.com/HabibTorjmen/Blockchain/tree/main/aztec-packages/.claude/skills/aztec-wallet
Command: npx skills add https://github.com/HabibTorjmen/Blockchain --skill aztec-wallet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction of operating a live Aztec L2 wallet by automatically resolving RPC endpoints, preparing the appropriate CLI-wallet tooling, and managing accounts and aliases so you can execute blockchain actions without manual setup.

Core Features & Use Cases

  • Network and RPC resolution: Accepts known networks (like next-net and testnet) or custom RPC URLs and normalizes them for execution.
  • End-to-end wallet operations: Delegates deploy, send, call (query), setup-account, and bridging workflows to the aztec-wallet agent.
  • Deterministic account handling: Uses a default private key (with specified salt) and coordinates shared working directory usage across multiple agent instances.
  • Alias conventions for safer addressing: Interprets contract/account references consistently via aliases such as accounts:default and contracts:<alias> to reduce user mistakes.

Quick Start

Ask it to run a transaction on a specific network, for example: Use the aztec-wallet skill on testnet to deploy TokenContract.

Frequently Asked Questions about aztec-wallet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an Aztec contract using natural language commands?

You can deploy an Aztec contract by stating your intent, which the skill translates into network-resolved, RPC-backed CLI execution. It delegates the deployment workflow to the aztec-wallet agent using a shared working directory and your PRIVATE_KEY.

Can I execute Aztec L2 transactions on a custom RPC endpoint?

Yes, you can execute Aztec L2 transactions on a custom RPC endpoint. The skill normalizes custom RPC URLs alongside predefined networks to run send workflows via the aztec-wallet agent.

What is needed to set up an Aztec account for bridging operations?

Setting up an Aztec account for bridging requires a PRIVATE_KEY and a specified SALT. The skill delegates the setup-account workflow to the aztec-wallet agent, ensuring deterministic account handling across operations.

How does alias management work for Aztec contract calls?

Alias management for Aztec contract calls uses conventions like accounts:default and contracts:<alias> to interpret references consistently. This reduces addressing mistakes when executing call and query workflows.

Are there limitations when running multiple aztec-wallet agent instances?

When running multiple aztec-wallet agent instances, you must coordinate a shared working directory per network. This prevents conflicts during contract deployment and transactions while maintaining deterministic account handling.