Agent skill · software engineering · jeremylongshore
quicknode-cost-tuning
Attribute and reduce QuickNode API-credit consumption by product, endpoint, method, chain, tag, and workload while preserving correctness. Use when forecasting a billing cycle, investigating an overage, or evaluating a caching or data-access change. Trigger with: "reduce QuickNode cost", "analyze QuickNode credits", "find expensive RPC methods".
Why this skill is useful
Provides specific implementation patterns and error handling for QuickNode's blockchain RPC that the AI wouldn't reliably generate on its own.
What it needs
Requires npm 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 Credit and Cost Control Overview Optimize measured API credits, not a guessed requests-per-dollar formula. Account billing periods and endpoint rolling metrics answer different questions, and Streams, Webhooks, SQL, and endpoints can have different consumption models. Prerequisites Billing window, plan, budget, and workload owner Access to Usage & Billing or authorized usage reads Product, endpoint, method, chain, and environment tags Instructions Step 1: Define the denominator Use Read and Grep to identify workloads, schedules, duplicate callers, cache policy, backfills, and high-cardinality queries. State whether the decision concerns the billing cycle or a rolling performance window. Step 2: Retrieve usage Use Bash(qn:) for authenticated usage and billing reads. Break consumption down by product and, where supported, endpoint, method, chain, or tag. Do not print invoices or account details into public logs. Step 3: Attribute value Map each large credit consumer to a product outcome and owner. Separate necessary live reads, historical backfills, retries, failed calls, polling, and abandoned experiments. Step 4: Choose a safe lever Use Write or Edit to cache immutable results, replace polling with an event product when justified, bound historical ranges, use pagination and selective fields, or schedule backfills. Never trade correctness for a lower request count silently. Step 5: Model the change Apply the account's current credit and pricing facts to measured volumes. Include plan limits, add-ons, flat-rate endpoints, and private terms only when verified; do not publish confidential pricing. Step 6: Verify one billing interval Compare expected and actual credits, errors, latency, freshness, and business completeness. Alert on both budget burn and missing work so a broken integration cannot look “cheap.” Tool Discipline Use Read and Grep for demand discovery, Bash(qn:) for read-only account usage, and Write/Edit for controlled optimizations. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/quicknode-cost-tuning--3a7791