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

/alchemy-security-basics

@820dfc8
Run it yourself

Analyze and secure Alchemy credentials, browser access, wallet authority, webhook verification, and untrusted chain data. Use when securing an Alchemy-backed application. Trigger with "secure Alchemy", "Alchemy API key exposure", or "verify an Alchemy webhook".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

referencesofficial-docs.md

≈743 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Alchemy Credential and Trust-Boundary Security: first-party evidence

Reviewed: 2026-09-12

Alchemy's current public documentation establishes the general service contract. The selected account, plan, application, credential, chain, endpoint, feature support, package lock, observed responses, and dashboard settings remain execution evidence for the actual environment.

Current contract notes

  • The alchemy-sdk JavaScript repository is archived and deprecated. New JavaScript EVM work uses viem; transacting applications and Portfolio support use @alchemy/wallet-apis; Solana work uses Solana Web3.js.
  • Application API keys, Admin access keys, Notify management tokens, webhook signing keys, and wallet signing authority are distinct. Never substitute one credential class for another.
  • RPC chain availability does not prove that a Data, NFT, Portfolio, Wallet, Simulation, or webhook feature is supported on that chain. Recheck both supported-chain and feature matrices.
  • Throughput is account-level and evaluated over a rolling ten-second token-bucket window. Method costs, plan capacity, pricing, and elastic-demand behavior are mutable; use current account evidence.
  • Portfolio fanout can return HTTP 200 with top-level error.partialErrors. Failed networks can be absent from pagination and require fresh, bounded retry requests.
  • Notify signatures use HMAC-SHA256 over the exact raw request body and the per-webhook signing key, with the digest in X-Alchemy-Signature.
  • Alchemy permits restricted frontend application-key patterns under current guidance, including allowlists, and recommends short-lived JWTs where appropriate. Admin, Notify, signing, and confidential server credentials do not move to the browser.
  • Skill invocation does not grant authority to access credentials or personal data, increase capacity or spend, change registrations, deploy, replay, sign, broadcast, rotate, revoke, or delete.

Evidence rules

  • Recheck linked first-party pages at execution and record source date plus account, application, chain, feature, endpoint, and version identities.
  • Prefer returned headers, request IDs, response states, dashboard observations, and account terms over remembered constants.
  • When first-party pages conflict or observed behavior differs, fail closed, preserve redacted evidence, and resolve the discrepancy before a side effect.

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 secure coding patterns and best practices for developing Web3 applications with Alchemy. It emphasizes protecting API keys, managing private keys via secret managers, and validating user inputs for blockchain queries.

  • 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
<application> <credential-class> <runtime>
version
2.0.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "alchemy",
  "security",
  "web3"
]
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-security-basics