Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/quicknode-install-auth

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/quicknode-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈90 tokens for metadata: the name and description. ≈884 when used: this file. ≈168 more on demand in 1 file.

Description uses 4.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈362 characters, or 4.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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, QN_SDK__API_KEY, 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 QN_SDK__API_KEY. 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. Rotate with overlap: create, deploy, verify, then revoke the old token.

Tool Discipline

Use Read and Grep for discovery, Write and Edit for secret references, Bash(qn:) for authenticated CLI identity checks, and Bash(curl:) only for redacted read probes. Never place a live endpoint URL in source, logs, shell history, or support evidence.

Output

  • Credential-to-client matrix
  • Environment-separated secret references
  • Negative and positive verification results
  • Rotation and revocation record

Examples

A production RPC service receives a dedicated endpoint token through its secret manager. A deployment auditor uses a separate x-api-key identity through the SDK and cannot submit chain transactions.

Error Handling

Failure Response
Endpoint returns unauthorized Verify endpoint token placement without logging it
Admin API returns 401 Verify the API key and account scope, not the RPC token
Token appears in a URL log Revoke it, sanitize retained logs, and replace it
Rotation breaks one consumer Restore the old secret reference during the overlap window

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides standard and safe instructions for integrating QuickNode blockchain RPC infrastructure, using established libraries and following best practices for secret management.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Edits files Runs commands
Modelinherit
version
2.0.0
argument-hint
[client-and-environment-scope]
model
inherit
All 6 allowed tools
ReadGrepWriteEditBash(qn:*)Bash(curl:*)
Other metadata
effort
high
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "saas",
  "quicknode",
  "blockchain",
  "authentication",
  "secrets"
]
compatibility
Requires a QuickNode account; Admin API and advanced endpoint-security features depend on the account plan

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/quicknode-install-auth