Agent skill

Alchemy Reference Architecture

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

Design a production Alchemy architecture with capability-specific adapters, explicit trust boundaries, partial-state semantics, and reversible operations.

MITAuto-check passedBackend & APIs

Install Alchemy Reference Architecture

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

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace alchemy-reference-architecture --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-reference-architecture .claude/skills/alchemy-reference-architecture && 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-reference-architecture
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
537 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Design a production Alchemy architecture with capability-specific adapters, explicit trust boundaries, partial-state semantics, and reversible operations.

  • Works in 6 steps: Inventory user journeys, data ownership,… → Draw trust and data-flow boundaries… → Define typed capability adapters with… → …
  • Creating an Alchemy-backed system
  • 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 Reference Architecture is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design a production Alchemy architecture with capability-specific adapters, explicit trust boundaries, partial-state semantics, and reversible operations. Use when reviewing or creating an Alchemy-backed system. Trigger with "Alchemy architecture", "design an Alchemy dApp backend", or "review Alchemy boundaries".

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 Smart contracts. 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

  • Creating an Alchemy-backed system
  • With Alchemy architecture
  • Design an Alchemy dApp backend
  • Review Alchemy boundaries

Example prompts

  • “Alchemy architecture”
  • “design an Alchemy dApp backend”
  • “review Alchemy boundaries”
  • “/alchemy-reference-architecture”

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. Inventory user journeys, data ownership, chains, Node/Data/Portfolio/Wallet/Notify/Admin capabilities, writes, callbacks, SLOs, and…
  2. Draw trust and data-flow boundaries including browser access, server adapters, queue, cache, database, secret store, observability…
  3. Define typed capability adapters with chain assertions, pagination, partial success, finality, idempotency, bounded retry, and…
  4. Keep read paths and transaction intent/signing paths separate; require simulation, policy, user consent, and audit receipts for writes.
  5. Design account-wide backpressure, cache freshness, webhook acknowledgement/replay, provider outage, status reconciliation, privacy…
  6. Threat-model and failure-test the design, map owners and approvals, then document incremental rollout and rollback variants.

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 Reference Architecture loads about 1.3k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 537 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
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.1k

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). 537 words, ~1,308 tokens.

Download SKILL.mdSave it as .claude/skills/alchemy-reference-architecture/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
alchemy-reference-architecture
description
Design a production Alchemy architecture with capability-specific adapters, explicit trust boundaries, partial-state semantics, and reversible operations. Use when reviewing or creating an Alchemy-backed system. Trigger with "Alchemy architecture", "design an Alchemy dApp backend", or "review Alchemy boundaries".
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-capabilities> <chain-set> <trust-model>
version
2.0.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, alchemy, architecture, governance
model
inherit
effort
high

Alchemy Production Reference Architecture

Overview

Design a production Alchemy architecture with capability-specific adapters, explicit trust boundaries, partial-state semantics, and reversible operations. 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

Current architecture separates EVM RPC through viem, Data APIs through typed HTTP adapters, Wallet APIs v5 through a transaction-policy boundary, Notify intake through authenticated idempotent queues, and Admin usage through restricted operations tooling. No shared archived SDK client or credential should collapse these contracts.

Authentication

Model browser, edge, API, worker, webhook, Admin, and signer identities separately. Application keys may serve permitted reads; Admin access keys, Notify tokens, webhook signing keys, and wallet signing authority remain isolated by runtime, owner, and policy.

Instructions

  1. Inventory user journeys, data ownership, chains, Node/Data/Portfolio/Wallet/Notify/Admin capabilities, writes, callbacks, SLOs, and regulatory constraints.
  2. Draw trust and data-flow boundaries including browser access, server adapters, queue, cache, database, secret store, observability, signer, provider, and external metadata.
  3. Define typed capability adapters with chain assertions, pagination, partial success, finality, idempotency, bounded retry, and unsupported-feature outcomes.
  4. Keep read paths and transaction intent/signing paths separate; require simulation, policy, user consent, and audit receipts for writes.
  5. Design account-wide backpressure, cache freshness, webhook acknowledgement/replay, provider outage, status reconciliation, privacy deletion, and cost controls.
  6. Threat-model and failure-test the design, map owners and approvals, then document incremental rollout and rollback variants.

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 (207 more words)Show less

Approval Boundaries

Architecture, security, product, operations, privacy/data, and budget owners approve their boundaries. Introducing a signer, browser credential, new retained data, or external provider requires explicit review.

Error Handling

  • Do not model Alchemy as one reliable box; show endpoint families, account limits, partial responses, indexing, and chain finality.
  • Do not let a queue acknowledgement imply successful downstream blockchain or user-visible processing.
  • Do not place Admin or signing credentials in the general application API tier.

Output

Return the context and data-flow diagrams, capability/client matrix, credential and ownership map, state/error contracts, SLO/capacity model, threat model, failure tests, rollout variants, and rollback plan. Mark assumptions, observations, source dates, environment-specific behavior, owners, and unresolved gaps explicitly.

Examples

  • Route a browser request through a server Portfolio adapter that preserves partial network state and caches only under an explicit freshness label.
  • Place Wallet APIs transaction construction and signer policy outside the read API so a compromised read key cannot authorize a transaction.

Validation

Exercise and record expected and observed results for:

  • browser boundary bypass
  • wrong chain
  • Portfolio partial success
  • queue duplicate
  • account saturation
  • signer unavailable

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-reference-architecture of jeremylongshore/tons-of-skills-marketplace.

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

Open the folder on GitHubat commit cfae287

Compare with similar skills

Alchemy Reference Architecture 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 Reference Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Alchemy Reference Architecture this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
Add Explorerlidofinance/diffyscan142—~1kAutomated safety check: PassMIT
Foundry Deploy Fixturesaviggiano/security144—~634Automated safety check: PassMIT
New Configlidofinance/diffyscan142—~1kAutomated safety check: PassMIT
Validate Configlidofinance/diffyscan142—~1.1kAutomated safety check: PassMIT
Ton Vulnerability Scannertrailofbits/skills7.5k—~3.8kAutomated safety check: PassCC-BY-SA-4.0

Similar skills

  • Add Explorer

    lidofinance/diffyscan

    Adds or repairs Diffyscan explorer API routing and response adapters for a new host, chain or payload format.

    142 GitHub stars~1k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • Foundry Deploy Fixtures

    aviggiano/security

    Create or refactor Foundry deployment fixtures for Solidity tests.

    144 GitHub stars~634 tokensUpdated 25 days ago
    Backend & APIsAuto-check passed
  • New Config

    lidofinance/diffyscan

    Creates or extends a Diffyscan verification config for a deployed contract or deployment.

    142 GitHub stars~1k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • Validate Config

    lidofinance/diffyscan

    Reviews an existing Diffyscan YAML or JSON config for load errors, runtime prerequisites, pinned sources, address mappings and broad exceptions.

    142 GitHub stars~1.1k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • Ton Vulnerability Scanner

    trailofbits/skills

    Official

    Scans TON (The Open Network) smart contracts for 3 critical vulnerabilities including integer-as-boolean misuse, fake Jetton contracts, and forward TON without gas checks.

    7.5k GitHub stars~3.8k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Verify Deployment PR

    OriginProtocol/origin-dollar

    Verifies a POST-EXECUTION mainnet (or other network) smart-contract deployment PR for this repo: confirms every deployed contract is listed in the PR description, that the on-chain verified source…

    153 GitHub stars~2.6k tokensUpdated 2 days ago
    Backend & APIsAuto-check: notes

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

Questions about Alchemy Reference Architecture

What does Alchemy Reference Architecture do?

Design a production Alchemy architecture with capability-specific adapters, explicit trust boundaries, partial-state semantics, and reversible operations. Alchemy Reference Architecture is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design a production Alchemy architecture with capability-specific adapters, explicit trust boundaries, partial-state semantics, and reversible operations.

When should I use Alchemy Reference Architecture?

Alchemy Reference Architecture fits situations like: creating an Alchemy-backed system; with Alchemy architecture; design an Alchemy dApp backend; review Alchemy boundaries.

How do I install Alchemy Reference Architecture in Claude Code?

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

How do I install Alchemy Reference Architecture in Codex?

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

Can I use Alchemy Reference Architecture 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-reference-architecture -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-reference-architecture, .gemini/skills/alchemy-reference-architecture, .github/skills/alchemy-reference-architecture and .opencode/skills/alchemy-reference-architecture in your project.

What does Alchemy Reference Architecture need to run?

SKILL.md names no scripts, command-line tools or credentials: Alchemy Reference Architecture 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 Reference Architecture 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 Reference Architecture 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 Reference Architecture use?

Alchemy Reference Architecture 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 Reference Architecture use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 793 tokens, read only when the agent opens those files.

What are the alternatives to Alchemy Reference Architecture?

Skills that share tags, products or a category with Alchemy Reference Architecture: Add Explorer (lidofinance/diffyscan, 142 stars), Foundry Deploy Fixtures (aviggiano/security, 144 stars), New Config (lidofinance/diffyscan, 142 stars) and Validate Config (lidofinance/diffyscan, 142 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Alchemy Reference Architecture?

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.