Agent skill · software engineering · jeremylongshore
quicknode-rate-limits
Analyze and govern QuickNode plan, IP, and method-specific rate limits without inventing a universal threshold. Use when requests receive QuickNode limit codes, one method needs a protective budget, or retry policy must respect endpoint controls. Trigger with: "analyze a QuickNode rate limit", "detect a method limit", "control QuickNode request bursts".
Why this skill is useful
Provides specific implementation patterns for handling QuickNode rate limits that the AI wouldn't reliably generate on its own.
What it needs
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 Rate-Limit Control Overview Treat account-plan ceilings, IP limits, and operator-configured method limits as separate controls. QuickNode exposes distinct JSON-RPC errors for per-second, per-minute, and method limits; an HTTP status alone is not sufficient diagnosis. Prerequisites Endpoint ID, plan, chain, network, and affected method A redacted error sample with HTTP and JSON-RPC fields Authorized dashboard, Admin API, or qn read access Authentication Authenticate qn interactively with qn auth login and verify the intended account with qn auth whoami. For direct Admin API inspection, inject a separate account API key as the x-api-key header. Endpoint tokens in URLs or x-token headers authenticate RPC traffic but do not replace control-plane credentials. Instructions Step 1: Classify the signal Use Read and Grep to find the first complete redacted response. Preserve QuickNode codes such as -32007 per-second, -32008 per-minute, and -32011 method limit. Separate client timeouts and chain-node errors. Step 2: Read the configured limits Use Bash(qn:) to inspect endpoint and method-rate settings through authenticated read commands. If the CLI version lacks the required view, use the dashboard or documented Admin API rather than guessing a number. Step 3: Measure demand Group requests by endpoint, token, source IP, method, and interval. Distinguish HTTP calls from WebSocket subscription creation; subscription responses do not count like new requests. Step 4: Choose the control Reduce concurrency, coalesce duplicate reads, cache immutable results, or set a method limit that protects expensive calls. Raising a plan limit is a capacity decision, not the first retry strategy. Step 5: Implement bounded retry Use Write or Edit to retry only idempotent reads and only recognized transient limit responses. Apply jitter, cap attempts and elapsed time, and honor a provider delay header when documented. Never automatically replay transaction submissions. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/quicknode-rate-limits--89934b