Agent skill · data analytics · jeremylongshore
quicknode-common-errors
Triage QuickNode transport, authentication, security-filter, capacity, chain, and application failures while preserving the original error layer. Use when RPC, SDK, or endpoint requests fail and ownership is unclear. Trigger with: "debug a QuickNode error", "QuickNode RPC failed", "classify a QuickNode error code".
Why this skill is useful
Provides specific error handling patterns and solutions for QuickNode RPC issues that the AI wouldn't reliably generate on its own.
What it needs
Requires ethers.js 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 Error Triage Overview Preserve HTTP status, JSON-RPC code, chain error, method, network, and request identifier as separate facts. Do not treat every -32000 family response as retryable or overwrite a contract revert with a provider diagnosis. Prerequisites A redacted failing request and response Endpoint ID, chain, network, protocol, and client version The expected method contract and a nearby successful request if available Instructions Step 1: Capture the first failure Use Read and Grep to locate the earliest complete failure before wrapper retries transform it. Redact endpoint tokens, API keys, signed transactions, addresses when sensitive, and request bodies not needed for diagnosis. Step 2: Assign the layer Classify DNS/TLS/timeout, HTTP authentication, QuickNode infrastructure, endpoint security, chain-node, smart-contract, or client-decoding failure. Keep nested causes intact. Step 3: Interpret QuickNode codes Recognize -32007 per-second limit, -32008 per-minute limit, -32011 method limit, -32604 empty or unsupported method, and -32611 endpoint security-filter rejection. Verify other codes against the chain-specific reference. Step 4: Inspect control-plane evidence Use Bash(qn:) for authenticated endpoint, metrics, or permitted error-log reads. Admin API endpoint logs are plan-gated; absence of access is not proof that no request reached QuickNode. Step 5: Run one discriminating test Compare a supported read method on the same endpoint, the same method with corrected parameters, or the same request in a non-production environment. Avoid retries that could resubmit a signed transaction. Step 6: Route ownership Assign the finding to credential owner, endpoint-security owner, capacity owner, chain integration, contract developer, or QuickNode support. Include only sanitized evidence and a reversible next action. Tool Discipline Use Read and Grep for local evidence and Bash(qn:) only for read-only account inspection. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/quicknode-common-errors--6a074f