Agent skill · software engineering · jeremylongshore
quicknode-local-dev-loop
Create a deterministic local QuickNode development loop with transport fixtures, base-URL injection, redacted recordings, and an opt-in read-only sandbox check. Use when developing SDK, RPC, Stream, or Webhook integrations without consuming live credits on every test. Trigger with: "develop against QuickNode locally", "mock QuickNode", "test a QuickNode adapter offline".
Why this skill is useful
Provides specific implementation patterns and error handling for QuickNode blockchain RPC integration 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 Deterministic Local Loop Overview Develop against an injectable transport by default. Local tests should model QuickNode protocol contracts without a live token, then use one explicit sandbox read to catch integration drift. Prerequisites Existing QuickNode or JSON-RPC adapter Repository test runner and fixture convention Optional non-production, read-only credential in a local secret manager Instructions Step 1: Locate the boundary Use Read and Grep to find direct endpoint calls, SDK constructors, global environment reads, retries, timers, and response parsing. Choose one adapter seam for injection. Step 2: Define fixture contracts Use Write or Edit to add success, HTTP error, JSON-RPC error, timeout, rate limit, malformed response, and pagination fixtures. Preserve request IDs and nested causes. Step 3: Inject transport and time Pass the transport, base URL, clock, and sleeper into the adapter. Use documented SDK base URL overrides only for a local stub or approved staging endpoint. Step 4: Sanitize recordings If a real response becomes a fixture, retain only necessary fields and replace endpoint URLs, tokens, API keys, addresses, and business payloads. Add a leak assertion to the fixture test. Step 5: Run fast tests Use Bash(npm:) to run the repository's pinned unit and contract commands. Keep network disabled in the default lane and make accidental outbound access fail. Step 6: Opt into one live read Gate a sandbox read behind an explicit variable or command. Verify chain identity and shape, cap timeout and calls, and skip cleanly when the opt-in credential is absent locally. Tool Discipline Use Read/Grep for adapter discovery, Write/Edit for injection and fixtures, and Bash(npm:) for repository-defined tests. Do not use production endpoints, funded signers, or live writes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/quicknode-local-dev-loop--b8456d