executing-agw-transactions

Enforce preview-first execution and explicit confirmation for Abstract Global Wallet transactions.

1|2|Updated Feb 18, 2026

Search Tags:#signing #dry-run #contract-interaction #token-transfer #agw-cli #transaction-preview #wallet-automation

Ready to run

npx skills add https://github.com/Abstract-Foundation/agw-cli --skill executing-agw-transactions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: executing-agw-transactions
Source: https://github.com/Abstract-Foundation/agw-cli/tree/main/packages/agw-cli/skills/executing-agw-transactions
Command: npx skills add https://github.com/Abstract-Foundation/agw-cli --skill executing-agw-transactions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of accidental, unauthorized state changes to your Abstract Global Wallet when AI agents perform signing, transfers, or contract interactions, by enforcing strict preview and confirmation workflows.

Core Features & Use Cases

Preview-first guardrails: All state-changing AGW actions require an explicit dry-run preview before execution, preventing unintended transaction broadcasts.
Schema-aligned payloads: Enforces use of official AGW command schemas to avoid malformed transaction inputs.
Explicit execute confirmation: Never infers execution permission from a successful preview, requiring explicit --execute flags for all mutating operations.
Use Case: If you ask an agent to deploy a smart contract to Abstract, the Skill first runs a dry-run to validate the bytecode and deployment parameters, then requires your explicit approval to broadcast the transaction.

Quick Start

Ask your AI agent to preview a 100 USDC transfer to vendor address 0x123abc before executing the transaction.

Frequently Asked Questions about executing-agw-transactions

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

FAQPage Schema

How do I prevent accidental token transfers when using AI agent wallet automation?▼

To prevent accidental token transfers during AI agent wallet automation, enforce preview-first execution rules that require an explicit dry-run preview before broadcasting any state-changing transaction. This schema-aligned validation ensures only intended mutating operations execute.

How do I execute a dry-run contract interaction before deployment?▼

You execute a dry-run contract interaction by applying preview-first guardrails that validate bytecode and deployment parameters before requiring explicit approval to broadcast the transaction. This prevents unintended contract deployment state changes.

Does Abstract Global Wallet signing require explicit confirmation for batched calls?▼

Abstract Global Wallet signing requires explicit confirmation for batched calls by enforcing strict preview and confirmation workflows. All batched calls, contract writes, and token transfers need a dry-run preview and an explicit execute flag before broadcasting.

What is the best way to validate AGW transaction payloads before broadcasting?▼

The best way to validate AGW transaction payloads before broadcasting is to enforce schema-aligned payload validation during a dry-run preview. This ensures transaction correctness by catching malformed inputs before explicit execution confirmation.

Why does a successful transaction preview not automatically execute the transfer?▼

A successful transaction preview does not automatically execute the transfer because explicit execute confirmation is required for all mutating operations. The system never infers execution permission from a preview, preventing unintended state changes to the wallet.