aabc-wallet-bridge

Validate tx_plans against the aabc-tx-plan schema and forward them to a connected wallet for signature.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/labsaistudio/AABC-Labs --skill aabc-wallet-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aabc-wallet-bridge
Source: https://github.com/labsaistudio/AABC-Labs/tree/main/backend/agent/skills/catalog/aabc-wallet-bridge
Command: npx skills add https://github.com/labsaistudio/AABC-Labs --skill aabc-wallet-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables third-party tools that generate transaction plans to hand them to a user's connected wallet for secure, user-approved signing, facilitating on-chain actions without exposing keys.

Core Features & Use Cases

  • tx_plan validation: ensures the tx_plan conforms to the required schema before submission.
  • wallet handoff: forwards the prepared tx_plan to the wallet for signature via the wallet-bridge endpoints.
  • phase-aware flow: supports Phase A doc-only workflow with guidance for Phase B when workspace runner ships.

Quick Start

Hand a prepared tx_plan to the user's connected wallet for signature.

Frequently Asked Questions about aabc-wallet-bridge

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

FAQPage Schema
How do I hand a tx plan to a user's connected wallet for signing?

A tx plan is handed to a user wallet for signing by forwarding the encoded transaction to exposed wallet-bridge endpoints, which validate the payload against the aabc-tx-plan schema and orchestrate the secure signature flow.

What is a tx plan validation schema in blockchain workflows?

Tx plan validation ensures a generated transaction conforms to the required aabc-tx-plan schema before submission, preventing malformed payloads from being forwarded to the user's connected wallet for signature.

Can I use third-party smart contract tooling to sign transactions without exposing private keys?

Yes, third-party smart contract tooling can generate encoded tx plans that are handed directly to the user's connected wallet for signature, facilitating secure on-chain actions without exposing private keys.

Do I need a workspace-runner available to broadcast mainnet transactions?

No, a workspace-runner is not required to process transactions, as this skill supports situations where a workspace-runner is not yet available by handing encoded tx plans directly to the user's connected wallet for signature.

What are the limitations when a workspace-runner is not yet available for web3 transactions?

When a workspace-runner is not yet available, the flow operates under a Phase A doc-only workflow limitation, with guidance provided for upgrading to a Phase B preview using the aabc-sign CLI when that runner ships.