One-click install
npx skills add https://github.com/tawf-labs/zkt-hackathon --skill qa-tawf-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/tawf-labs/zkt-hackathon/tree/main/.agents/skills/ethskills/qa
Command: npx skills add https://github.com/tawf-labs/zkt-hackathon --skill qa-tawf-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents Ethereum dApp release mistakes by validating wallet flow, network switching, transaction gating, and production UX details before users ever test the build.

Core Features & Use Cases

  • Wallet flow correctness checks: Ensures the app shows a Connect Wallet button (not text), enforces the four-state primary CTA flow, and prevents duplicate submissions during pending windows.
  • Production readiness validation: Verifies branding removal (Scaffold-ETH 2 template artifacts), contract address visibility, address input correctness, USD value rendering, OG image URL format, and polling/RPC configuration.
  • Operational safety and trust signals: Confirms block explorer source-code verification, proper error surfacing, theme compliance (no hardcoded dark backgrounds), and mobile deep-link behavior after the transaction is relayed.

Quick Start

Send the qa skill to a separate reviewer agent after the zkt-hackathon build completes to perform a PASS/FAIL pre-ship audit without modifying code.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I validate Ethereum dApp readiness before production deployment?

To validate Ethereum dApp readiness, audit wallet connection UX, network switching, transaction button gating, and production configuration details. This requires source code reading and browser click-through of all flows to verify deterministic CTA behavior and reliable RPC integration.

What is the correct primary CTA flow for a Scaffold-ETH 2 Next.js dApp?

The correct primary CTA flow for a Scaffold-ETH 2 Next.js dApp enforces a four-state transition on the Connect Wallet button, prevents duplicate submissions during pending windows, and ensures one-primary-button state transitions using correct scaffold write hooks.

How do I check wallet connection UX and transaction gating in an EVM dApp?

Checking wallet connection UX and transaction gating involves verifying the app shows a Connect Wallet button instead of text, confirming safe loading states, validating correct address input components, and ensuring approval buttons gate transactions properly to prevent duplicate submissions.

Does the dApp QA audit verify block explorer source-code and mobile deep linking?

Yes, the dApp QA audit confirms block explorer source-code verification for deployed contracts and checks mobile deep-link behavior after transactions are relayed, alongside verifying OG image URL formats and polling/RPC configuration for operational safety.

Can I use this production readiness validation for non-Scaffold-ETH EVM UIs?

Yes, this production readiness validation applies to other EVM UIs beyond Scaffold-ETH 2 style Next.js dApps, specifically where deterministic CTA behavior and reliable RPC/wallet integration are required for correct transaction gating and wallet flow operations.

Why does my Ethereum dApp fail the pre-ship checklist audit?

An Ethereum dApp fails the pre-ship checklist if it retains Scaffold-ETH 2 template branding artifacts, uses hardcoded dark backgrounds breaking theme compliance, lacks contract address visibility, or has incorrect USD value rendering and unverified block explorer deployments.