Agent skill

Alchemy Install Auth

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Select and prove the current Alchemy client, key type, network, and authentication boundary before integration work.

MITAuto-check passedBackend & APIs

Install Alchemy Install Auth

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill alchemy-install-auth -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace alchemy-install-auth --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/alchemy-install-auth .claude/skills/alchemy-install-auth && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
alchemy-install-auth
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
609 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Select and prove the current Alchemy client, key type, network, and authentication boundary before integration work.

  • Works in 6 steps: Classify the requested capability as… → Confirm the required chain and feature… → Select viem, direct HTTP,… → …
  • Repairing Alchemy connectivity
  • SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Alchemy Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Select and prove the current Alchemy client, key type, network, and authentication boundary before integration work. Use when creating or repairing Alchemy connectivity. Trigger with "set up Alchemy", "configure an Alchemy API key", or "choose viem or Wallet APIs".

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval

It sits in Backend & APIs, covering Authentication. It works with viem and wagmi and Solana. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Repairing Alchemy connectivity
  • With set up Alchemy
  • Configure an Alchemy API key

Example prompts

  • “set up Alchemy”
  • “configure an Alchemy API key”
  • “choose viem or Wallet APIs”
  • “/alchemy-install-auth”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Classify the requested capability as Node RPC, Data API, Portfolio, Wallet APIs, Notify management, webhook receipt, Admin usage, or Solana.
  2. Confirm the required chain and feature in the live supported-chain and feature-support matrices; do not infer feature parity from RPC…
  3. Select viem, direct HTTP, @alchemy/wallet-apis, or Solana Web3.js from the capability—not from the archived SDK examples.
  4. Create or identify a non-production application and a least-privilege key; separately identify any Admin access key or Notify token…
  5. Configure the credential through the repository's established secret mechanism and document whether requests use a server header, server…
  6. Run one read-only chain-specific proof, record the redacted request shape and response, then document rotation, revocation, owner…

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval

    From compatibility in the SKILL.md frontmatter.

Context cost

Alchemy Install Auth loads about 1.3k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 72 tokens; SKILL.md has 609 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 609 words, ~1,339 tokens.

Download SKILL.mdSave it as .claude/skills/alchemy-install-auth/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
alchemy-install-auth
description
Select and prove the current Alchemy client, key type, network, and authentication boundary before integration work. Use when creating or repairing Alchemy connectivity. Trigger with "set up Alchemy", "configure an Alchemy API key", or "choose viem or Wallet APIs".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval
argument-hint
<product-api> <chain> <environment>
version
2.0.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, alchemy, authentication, web3
model
inherit
effort
high

Alchemy Installation and Authentication Intake

Overview

Select and prove the current Alchemy client, key type, network, and authentication boundary before integration work. 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

The legacy alchemy-sdk JavaScript repository is archived and deprecated. New EVM reads use viem or direct documented HTTP APIs; transacting applications and Portfolio support use @alchemy/wallet-apis; Solana work uses Solana Web3.js. An application API key, an Admin access key, a Notify auth token, and a webhook signing key are different credentials and are not interchangeable.

Authentication

Prefer server-side request-header authentication for confidential workloads. A browser key is acceptable only when the current Alchemy guidance, explicit domain allowlists, least privilege, and the product threat model allow it; short-lived JWTs are the stronger frontend option. Store Admin, Notify, webhook, and signing credentials only in approved secret storage.

Instructions

  1. Classify the requested capability as Node RPC, Data API, Portfolio, Wallet APIs, Notify management, webhook receipt, Admin usage, or Solana.
  2. Confirm the required chain and feature in the live supported-chain and feature-support matrices; do not infer feature parity from RPC support.
  3. Select viem, direct HTTP, @alchemy/wallet-apis, or Solana Web3.js from the capability—not from the archived SDK examples.
  4. Create or identify a non-production application and a least-privilege key; separately identify any Admin access key or Notify token actually required.
  5. Configure the credential through the repository's established secret mechanism and document whether requests use a server header, server URL, or approved restricted browser boundary.
  6. Run one read-only chain-specific proof, record the redacted request shape and response, then document rotation, revocation, owner transfer, and environment separation.

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.

Show full SKILL.md (233 more words)Show less

Approval Boundaries

The application owner selects the product and chain. Security approves any browser credential boundary and production secret store. Creating, rotating, revoking, or deleting a live key requires explicit approval from its owner.

Error Handling

  • A valid key on an unsupported feature or chain is not a successful setup.
  • Do not substitute an application API key for an Admin access key, Notify token, or webhook signing key.
  • If a secret appears in source, logs, or artifacts, stop, revoke or rotate it, remove the exposure, and preserve a redacted incident receipt.

Output

Return the capability-to-client decision, chain/feature proof, credential-class matrix, redacted connectivity result, secret lifecycle, owners, evidence date, and unresolved gaps. Mark assumptions, observations, source dates, environment-specific behavior, owners, and unresolved gaps explicitly.

Examples

  • For a server-rendered Ethereum balance view, select viem, prove one read with a development app key, and keep the production key in the server secret boundary.
  • For a transacting smart-wallet application, select Wallet APIs v5 and reject an archived alchemy-sdk bootstrap even if an old repository still imports it.

Validation

Exercise and record expected and observed results for:

  • wrong chain
  • unsupported feature on a supported chain
  • missing or invalid key
  • application key supplied to an Admin endpoint
  • revoked key
  • secret-canary scan

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.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/alchemy-install-auth of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Alchemy Install Auth next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Alchemy Install Auth compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Alchemy Install Auth this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
Alchemy Agentic Gatewaymoonpay/skills113—~2.1kAutomated safety check: NotesMIT
NEAR Intents Swap Integrationinternet-court/internet-court-skill6.6k1 repos~939Automated safety check: PassCustom licence
Bridge Tokenscirclefin/skills155—~4.5kAutomated safety check: NotesApache-2.0
Venice Authveniceai/skills144—~4.4kAutomated safety check: PassMIT
Use User Controlled Walletscirclefin/skills155—~3.6kAutomated safety check: NotesApache-2.0

Similar skills

  • A skill your agent uses when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features.

    113 GitHub stars~2.1k tokensUpdated 1 mo ago
    Backend & APIsAuto-check: notes
  • NEAR Intents Swap Integration

    internet-court/internet-court-skill

    Builds cross-chain token swaps and bridge flows with the NEAR Intents 1Click API: quotes, deposit addresses, per-chain deposits and status polling.

    6.6k GitHub starsUsed in 1 repo~939 tokens
    Backend & APIsAuto-check passed
  • Bridge Tokens

    circlefin/skills

    Build browser or server token bridging across chains with Circle App Kit or standalone Bridge Kit.

    155 GitHub stars~4.5k tokensUpdated yesterday
    Backend & APIsAuto-check: notes
  • Venice Auth

    veniceai/skills

    Authenticate to the Venice API with a Bearer API key or with an x402 / SIWX wallet (EVM on Base, including EIP-1271 smart wallets, or Ed25519 on Solana).

    144 GitHub stars~4.4k tokensUpdated 5 days ago
    Backend & APIsAuto-check passed
  • Build non-custodial wallets where end users retain control of their private keys via Circle's user-controlled wallets SDK.

    155 GitHub stars~3.6k tokensUpdated yesterday
    Backend & APIsAuto-check: notes
  • Integration Privy

    aiskillstore/marketplace

    Add Privy authentication to a Solana Expo Android app on top of Mobile Wallet Adapter, using Sign-In-With-Solana.

    433 GitHub stars~2.6k tokensUpdated yesterday
    MobileAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Alchemy Install Auth

What does Alchemy Install Auth do?

Select and prove the current Alchemy client, key type, network, and authentication boundary before integration work. Alchemy Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Select and prove the current Alchemy client, key type, network, and authentication boundary before integration work.

When should I use Alchemy Install Auth?

Alchemy Install Auth fits situations like: repairing Alchemy connectivity; with set up Alchemy; configure an Alchemy API key.

How do I install Alchemy Install Auth in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill alchemy-install-auth -a claude-code`. Or copy the skill folder (skills/.curated/alchemy-install-auth in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/alchemy-install-auth in your project. Claude Code loads it when a task matches its description.

How do I install Alchemy Install Auth in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill alchemy-install-auth -a codex`. Or copy the skill folder (skills/.curated/alchemy-install-auth in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/alchemy-install-auth in your project. Codex loads it when a task matches its description.

Can I use Alchemy Install Auth in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill alchemy-install-auth -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/alchemy-install-auth, .gemini/skills/alchemy-install-auth, .github/skills/alchemy-install-auth and .opencode/skills/alchemy-install-auth in your project.

What does Alchemy Install Auth need to run?

SKILL.md names no scripts, command-line tools or credentials: Alchemy Install Auth is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval.

Does Alchemy Install Auth access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Alchemy Install Auth safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Alchemy Install Auth use?

Alchemy Install Auth is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Alchemy Install Auth use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 817 tokens, read only when the agent opens those files.

What are the alternatives to Alchemy Install Auth?

Skills that share tags, products or a category with Alchemy Install Auth: Alchemy Agentic Gateway (moonpay/skills, 113 stars), NEAR Intents Swap Integration (internet-court/internet-court-skill, 6.6k stars), Bridge Tokens (circlefin/skills, 155 stars) and Venice Auth (veniceai/skills, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Alchemy Install Auth?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.