--- name: quicknode-hello-world-5be4a65b23c6 description: 'Prove a new QuickNode RPC endpoint with a minimal, read-only JSON-RPC contract before application integration. Use when onboarding a chain endpoint or separating provider failures from client-library failures. Trigger with: "test my QuickNode endpoint", "make the first QuickNode request", "verify QuickNode RPC".' allowed-tools: Read, Grep, Write, Edit, Bash(curl:*) version: 2.0.0 argument-hint: '[chain-and-network]' model: inherit effort: medium license: MIT author: Jeremy Longshore tags: - saas - quicknode - blockchain - json-rpc - verification compatibility: 'Requires a QuickNode HTTP endpoint and a documented read method for the selected chain' --- # QuickNode Read-Only Endpoint Proof ## Overview Establish transport, authentication, chain identity, response shape, and tip movement with raw JSON-RPC before adding an SDK. This keeps the first proof deterministic and prevents a client-library configuration error from looking like an endpoint outage. ## Prerequisites - A secret reference for the QuickNode endpoint and token - The expected chain, network, protocol, and chain identifier - A non-sensitive read method supported by that chain ## Instructions ### Step 1: Inspect the integration Use Read and Grep to find the endpoint variable, expected chain ID, timeout, and current client wrapper. Stop if source or logs contain a literal QuickNode token. ### Step 2: Define the probe Use Write or Edit to create a small fixture containing only JSON-RPC version, a read method, empty parameters when valid, and a stable request ID. For EVM, pair `eth_chainId` with `eth_blockNumber`; do not submit a transaction. ### Step 3: Call through the secret boundary Use Bash(curl:*) with a timeout, JSON content type, and the endpoint injected by the runtime. Suppress verbose output because the URL may contain a token. ```bash curl --silent --show-error --max-time 10 \ --header 'content-type: application/json' \ --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}' \ "$QUICKNODE_ENDPOINT" ``` ### Step 4: Validate semantics Require HTTP success, matching JSON-RPC `id`, exactly one of `result` or `error`, and the expected chain ID. Parse hexadecimal block numbers explicitly rather than comparing their strings. ### Step 5: Prove liveness Read the latest block twice with a chain-appropriate interval. Tip movement is useful evidence but is not universal during quiet or halted networks, so compare against the chain status before declaring failure. ### Step 6: Capture a safe receipt Record timestamp, chain, network, method, latency, HTTP status, JSON-RPC error code if any, and redacted endpoint identity. Never retain the endpoint URL. ## Tool Discipline Use Read and Grep for configuration discovery, Write and Edit for a non-secret probe fixture, and Bash(curl:*) for bounded reads. Do not use this workflow for writes, signing, or funded keys. ## Output - Endpoint contract and expected chain identity - Redacted transport and JSON-RPC receipt - Liveness result with chain-status context - Clear owner for any failed layer ## Examples An Ethereum mainnet endpoint returns chain ID `0x1` and a valid block number. A response from a testnet is rejected even though transport and authentication succeeded. ## Error Handling | Failure | Response | | --- | --- | | HTTP 401 or 403 | Check token type, security filters, and secret injection | | JSON-RPC error | Preserve code and message after redaction; do not flatten it to HTTP | | Wrong chain ID | Stop deployment and correct endpoint selection | | Timeout | Compare provider status and a second bounded read before escalation | ## Resources - [Endpoint-proof evidence and source notes](references/official-docs.md) - [Ethereum quickstart](https://www.quicknode.com/docs/ethereum/quickstart) - [QuickNode APIs](https://www.quicknode.com/docs/build-with-ai/quicknode-apis) --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/quicknode-pack/skills/quicknode-hello-world/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/quicknode-pack/skills/quicknode-hello-world/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Backend Developer, Data Engineer, ML / AI Engineer Specialties: API, Design, Word Documents, Frontend Tools: Ethers, Quicknode Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: e854d9e4d488f2dce8a93c0217c42efa2a9be19368d351246f222903373ef0f7