transaction-auditor

Synchronize local Zod schemas and audit transaction state machines against the Andamio Gateway API.

5|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Andamio-Platform/andamio-app-template --skill transaction-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: transaction-auditor
Source: https://github.com/Andamio-Platform/andamio-app-template/tree/main/.claude/skills/transaction-auditor
Command: npx skills add https://github.com/Andamio-Platform/andamio-app-template --skill transaction-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill ensures your application's transaction schemas remain synchronized with the Andamio Gateway API, preventing critical bugs and ensuring smooth transaction processing.

Core Features & Use Cases

  • Schema Synchronization: Automatically fetches the latest API specifications to update local Zod schemas and type definitions.
  • TX State Machine Auditing: Verifies that transaction states, particularly the non-terminal nature of 'confirmed', are correctly handled in the frontend.
  • Use Case: After a new Andamio Gateway API release, run this Skill to update your app's transaction types and validate that your UI correctly waits for the 'updated' state before considering a transaction complete, preventing stale data issues.

Quick Start

Run the transaction auditor skill to sync schemas from the gateway API.

Frequently Asked Questions about transaction-auditor

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

FAQPage Schema
How do I sync local transaction schemas with an evolving blockchain API?

To sync local transaction schemas, fetch the latest API specifications to update local Zod schemas and type definitions. This ensures your application's transaction processing aligns with the updated blockchain gateway protocols.

Why does my dApp UI show stale data after a transaction is confirmed?

Your dApp UI might show stale data if it treats the 'confirmed' state as terminal. You must audit the transaction state machine to verify the UI waits for the 'updated' state and correctly triggers onComplete callbacks.

What is transaction state machine auditing in a Cardano dApp?

Transaction state machine auditing verifies that transaction states and onComplete callbacks are correctly handled in the frontend. It specifically checks the non-terminal nature of 'confirmed' states to prevent stale data issues in the dApp.

When do I need to update Zod schemas and TX_TYPE_MAP for my dApp?

You need to update Zod schemas and TX_TYPE_MAP after a new Gateway API release. Running an audit synchronizes your local types with the new specification, maintaining dApp integrity with evolving protocols.

Can I validate terminal states and onComplete callbacks against the Gateway API?

Yes, you can validate terminal states and onComplete callbacks by auditing the transaction state machine against the API specification. This verifies critical state machine logic to prevent stale data issues.