Agent skill · software engineering · jeremylongshore
quicknode-deploy-integration
Deploy a QuickNode integration with environment-scoped endpoints, preflight reads, staged traffic, observability, and reversible credential cutover. Use when releasing a new RPC endpoint, SDK client, Stream, or Webhook consumer. Trigger with: "deploy QuickNode", "roll out a QuickNode endpoint", "canary a QuickNode integration".
Why this skill is useful
Provides specific implementation patterns and error handling for QuickNode 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 Deployment Gate Overview Release configuration before traffic, prove the selected chain and product contracts, then increase exposure in stages. Keep old endpoints or tokens available through a bounded rollback window. Prerequisites Release commit, target environment, endpoint and product inventory Secret-manager references for environment-specific credentials SLO, canary cohort, rollback owner, and maximum cutover window Instructions Step 1: Audit the release Use Read and Grep to find endpoint variables, literal URLs, chain IDs, network names, SDK versions, write paths, Stream/Webhook destinations, and timeout/retry changes. Step 2: Validate control-plane state Use Bash(qn:) for read-only endpoint, Stream, Webhook, security, usage, and metrics inspection. Confirm target resources exist and are active without changing status. Step 3: Render safe configuration Use Write or Edit to bind environment-specific secret references, expected chain identity, finite timeouts, bounded concurrency, and feature flags. Keep endpoint tokens out of artifacts and client bundles. Step 4: Run preflight Execute contract tests and one protected read-only request. For event products, use their test or preview path and confirm destination acknowledgement without creating business effects. Step 5: Canary traffic Shift a small declared cohort, then compare latency percentiles, error layers, chain identity, credit use, transaction landing or event completeness, and downstream queue health. Step 6: Promote or roll back Promote only when acceptance thresholds hold for the declared window. Roll back configuration and traffic before revoking the old credential; rotate compromised credentials immediately. Tool Discipline Use Read/Grep for release discovery, Write/Edit for reviewed configuration, and Bash(qn:) for read-only control-plane evidence. Production mutation and traffic shifts require an explicit operator checkpoint. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/quicknode-deploy-integration