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

/alchemy-common-errors

@820dfc8
Run it yourself

Classify Alchemy authentication, JSON-RPC, Data API, throughput, and partial-response failures before applying bounded recovery. Use when an Alchemy integration fails or degrades. Trigger with "Alchemy error", "Alchemy 429", or "debug an Alchemy request".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/alchemy-common-errors

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈70 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈794 more on demand in 1 file.

Description uses 3.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 ≈279 characters, or 3.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.

Alchemy Error Classification and Recovery

Overview

Classify Alchemy authentication, JSON-RPC, Data API, throughput, and partial-response failures before applying bounded recovery. This workflow produces a reviewable artifact and negative-path evidence before any live side effect.

Prerequisites

  • Current first-party Alchemy documentation for the selected product, chain, feature, client, authentication method, limit, and lifecycle.
  • Named product, application, security, data/privacy, budget, release, and operations owners appropriate to the requested scope.
  • Synthetic or approved non-production fixtures, a credential canary, explicit success criteria, and a tested rollback boundary.

Current Contract

Alchemy surfaces transport status, JSON-RPC error objects, product-specific errors, and—in Portfolio workflows—partial errors inside an HTTP 200 response. Recovery depends on idempotency and failure class. Current limits and method availability are account, product, network, and time dependent; static plan tables are not diagnostic authority.

Authentication

Collect only a credential fingerprint or key identifier, never the credential. Verify application state, network, allowlists, endpoint family, and credential class in the dashboard or approved inventory without copying secrets into commands or tickets.

Instructions

  1. Capture timestamp, endpoint family, network, method, sanitized parameters, HTTP status, JSON-RPC code, response headers, request ID, attempt count, and affected SLO.
  2. Classify the failure as local validation, authentication/policy, unsupported method/network, throughput/quota, provider transient, deterministic RPC rejection, partial response, or downstream parsing.
  3. Reproduce with a synthetic or public fixture and the same environment class; compare current service status, feature support, and account usage.
  4. Correct invalid inputs or routing without retry; honor retry guidance for transient or throughput failures within an idempotency-aware budget.
  5. For partial success, retain successful partitions and retry only failed partitions using their documented fresh-request contract.
  6. Verify recovery and the exhaustion path, redact the evidence bundle, and escalate persistent provider failures with the request ID.

Tool Discipline

Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, wallet addresses, customer data, plan changes, spend, key creation or rotation, webhook changes, deployment, replay, transaction construction, signing, broadcast, or deletion.

Approval Boundaries

Operations owns retry budgets and degraded behavior. Security owns credential incidents. Raising throughput, changing plans, replaying writes, or moving traffic to another provider requires the relevant budget/release approval.

Error Handling

  • A retry cannot repair invalid parameters, unsupported features, or the wrong credential class.
  • Do not log request URLs that embed an API key or full user payloads.
  • Do not interpret HTTP 200 as complete success for endpoints that can return partial errors.

Output

Return the redacted failure envelope, classification, current evidence, causal hypothesis, bounded repair, negative-path result, unresolved impact, owner, and escalation receipt. Mark assumptions, observations, source dates, environment-specific behavior, owners, and unresolved gaps explicitly.

Examples

  • Classify a 429 using observed headers and account usage, then prove both a bounded recovery and a user-visible exhausted state.
  • Classify a Portfolio HTTP 200 with partialErrors as degraded partial success, not a successful complete portfolio.

Validation

Exercise and record expected and observed results for:

  • invalid params
  • wrong key class
  • unsupported network
  • 429 with retry guidance
  • transient 5xx
  • HTTP 200 partial failure

Resources

  • Current first-party evidence map — recheck dated Alchemy sources before execution.
  • Treat observed account, application, network, indexer, chain, or provider behavior as environment-specific evidence, never a universal guarantee.

Source: SKILL.md on GitHub

No rule matched.

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

    This skill provides diagnostic instructions and code snippets for troubleshooting Alchemy SDK and Web3 API errors. It emphasizes security best practices, such as sanitizing logs and using environment variables for API keys. A minor surface for indirect prompt injection exists because the skill processes external network logs and API responses while having access to shell tools, though it includes explicit instructions for data sanitization.

  • 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 yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<sanitized-request-id> <endpoint-class> <symptom>
version
2.0.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "alchemy",
  "troubleshooting",
  "reliability"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/alchemy-common-errors