Agent skill · software engineering · jeremylongshore
quicknode-install-auth
Choose and configure the correct QuickNode credential boundary for RPC endpoints, the Admin API, the unified SDK, and the qn CLI. Use when onboarding an endpoint, separating environments, or rotating access without exposing tokens. Trigger with: "authenticate QuickNode", "configure a QuickNode endpoint", "rotate QuickNode credentials".
Why this skill is useful
Adds specific commands and configurations for integrating QuickNode with blockchain applications that the AI wouldn't reliably generate on its own.
What it needs
Requires node 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 Credential Boundary Overview Separate data-plane endpoint tokens from account-level API keys. An endpoint token authorizes chain RPC traffic; an API key authorizes QuickNode product and control-plane clients such as Admin API, Streams, the unified SDK, and qn. Prerequisites The client, chain, network, environment, and required QuickNode products An approved secret manager and named rotation owner A QuickNode account role permitted to create only the required credential Instructions Step 1: Inventory credential consumers Use Read and Grep to locate endpoint URLs, x-token, x-api-key, QNSDKAPIKEY, and QUICKNODE references. Record owners without printing values. Treat any token embedded in an RPC URL as secret material. Step 2: Select the credential type Use an endpoint authentication token for HTTP or WSS chain RPC. Prefer the x-token header for server-side clients when the chain endpoint supports it. Use a dashboard API key for Admin API, SDK, Streams, Webhooks, KV Store, or SQL Explorer access. Step 3: Separate environments Give development, staging, production, and independent applications separate endpoint tokens. Multi-token authentication permits revoking one consumer without rotating every workload. Do not reuse a human CLI session as a production service identity. Step 4: Configure clients safely Use Write or Edit to add secret references and documented variable names, never values. Configure the unified SDK with QNSDKAPIKEY. Use Bash(qn:) for qn auth login and qn auth whoami only in an approved interactive operator session. Step 5: Verify the intended boundary Use Bash(curl:) for one read-only JSON-RPC probe with the token supplied by the runtime secret mechanism. Confirm the chain identifier and an expected denial after removing the credential; never echo the endpoint URL or request headers. Step 6: Record rotation Document credential type, endpoint or API scope, consumers, storage reference, creation date, review date, and revoke-first rollback. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/quicknode-install-auth