Agent skill · software engineering · jeremylongshore
quicknode-hello-world
Prove a new QuickNode RPC endpoint with a minimal, read-only JSON-RPC contract before application integration. Use when onboarding a chain endpoint or separating provider failures from client-library failures. Trigger with: "test my QuickNode endpoint", "make the first QuickNode request", "verify QuickNode RPC".
Why this skill is useful
Provides specific commands and code snippets 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 Read-Only Endpoint Proof Overview Establish transport, authentication, chain identity, response shape, and tip movement with raw JSON-RPC before adding an SDK. This keeps the first proof deterministic and prevents a client-library configuration error from looking like an endpoint outage. Prerequisites A secret reference for the QuickNode endpoint and token The expected chain, network, protocol, and chain identifier A non-sensitive read method supported by that chain Instructions Step 1: Inspect the integration Use Read and Grep to find the endpoint variable, expected chain ID, timeout, and current client wrapper. Stop if source or logs contain a literal QuickNode token. Step 2: Define the probe Use Write or Edit to create a small fixture containing only JSON-RPC version, a read method, empty parameters when valid, and a stable request ID. For EVM, pair ethchainId with ethblockNumber; do not submit a transaction. Step 3: Call through the secret boundary Use Bash(curl:) with a timeout, JSON content type, and the endpoint injected by the runtime. Suppress verbose output because the URL may contain a token. Step 4: Validate semantics Require HTTP success, matching JSON-RPC id, exactly one of result or error, and the expected chain ID. Parse hexadecimal block numbers explicitly rather than comparing their strings. Step 5: Prove liveness Read the latest block twice with a chain-appropriate interval. Tip movement is useful evidence but is not universal during quiet or halted networks, so compare against the chain status before declaring failure. Step 6: Capture a safe receipt Record timestamp, chain, network, method, latency, HTTP status, JSON-RPC error code if any, and redacted endpoint identity. Never retain the endpoint URL. Tool Discipline Use Read and Grep for configuration discovery, Write and Edit for a non-secret probe fixture, and Bash(curl:) for bounded reads. Do not use this workflow for writes, signing, or funded keys. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/quicknode-hello-world