Agent skill · software engineering · jeremylongshore
quicknode-core-workflow-a
Design a safe EVM transaction-submission path over QuickNode with simulation, fee and nonce policy, signer isolation, broadcast identity, and confirmation rules. Use when moving a read-only integration into transaction writes. Trigger with: "send transactions through QuickNode", "build an EVM write path", "harden QuickNode transaction submission".
Why this skill is useful
Provides specific commands and workflows for interacting with QuickNode's blockchain RPC that the AI wouldn't reliably generate on its own.
What it needs
Requires ethers installed locally. Requires quicknode account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
QuickNode EVM Transaction Safety Overview Build a write path that treats signing, submission, and confirmation as separate state transitions. QuickNode transports the signed transaction; the application remains responsible for intent, signer custody, nonce coordination, chain identity, and reorganization policy. Prerequisites A verified QuickNode endpoint and expected EVM chain ID A testnet signer held outside source code Contract ABI, write intent, value ceiling, and confirmation policy Instructions Step 1: Inspect the existing path Use Read and Grep to find signers, private-key variables, nonce overrides, fee logic, retries, and receipt assumptions. Stop if secrets or signed raw transactions are logged. Step 2: Define transaction intent Use Write or Edit to express destination, calldata, value, chain ID, and caller policy as validated inputs. Reject unexpected networks and unbounded value before reaching the signer. Step 3: Simulate and estimate Run the equivalent read call and gas estimate at an explicit block tag when supported. Treat a revert as an application or chain-state result, not a transient provider failure. Step 4: Coordinate nonce and fees Assign one nonce owner per signer. Read pending nonce state, define replacement rules, and use chain-appropriate fee fields. Do not blindly overwrite a nonce or double fees on each timeout. Step 5: Sign and broadcast once Keep signing in a wallet, HSM, or approved remote signer. Persist the signed transaction hash before submission. On an ambiguous timeout, query by hash before broadcasting again. Step 6: Confirm by policy Track inclusion, receipt status, block hash, and the required chain-specific confirmation depth. Reconcile dropped or reorganized receipts and expose a durable business-operation idempotency key. Tool Discipline Use Read and Grep for transaction-path discovery and Write/Edit for validation, state-machine, and tests. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/quicknode-core-workflow-a