---
name: alchemy-prod-checklist
description: >-
  Make an evidence-backed go or no-go decision for an Alchemy-backed production release. Use when reviewing a launch or material integration change. Trigger with "Alchemy production checklist", "Alchemy go-live review", or "is this Alchemy integration ready".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<release-sha> <environment> <change-scope>"
version: 2.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [ saas, alchemy, production, governance ]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval"
title: alchemy-prod-checklist
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/alchemy-prod-checklist
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/alchemy-prod-checklist/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/alchemy-prod-checklist`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/alchemy-prod-checklist`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/alchemy-prod-checklist) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/alchemy-prod-checklist`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/alchemy-prod-checklist --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/alchemy-prod-checklist --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Alchemy Production Readiness Decision

## Overview

Make an evidence-backed go or no-go decision for an Alchemy-backed production release. 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

Production readiness is a signed decision over a specific artifact, environment, Alchemy application, chain and feature set, account contract, data path, SLOs, and rollback. A passing connectivity check or testnet transaction does not authorize production traffic or wallet operations.

## Authentication

Confirm owners and lifecycle for every application key, Admin key, Notify token, webhook signing key, and signer. Prove environment isolation, least privilege, rotation, revocation, log redaction, and break-glass access.

## Instructions

1. Freeze the release SHA and enumerate Node, Data, Portfolio, Wallet, Notify, Admin, chain, address/data, and transaction surfaces in scope.
2. Recheck current first-party feature support, errors, throughput, pricing, and SDK/client guidance; record account-specific observations and dates.
3. Verify deterministic tests, contract fixtures, chain assertions, partial/pagination handling, bounded retries, idempotency, and provider-outage behavior.
4. Review secret, privacy, webhook, wallet-signer, dependency, artifact, and supply-chain evidence plus incident and key-rotation exercises.
5. Review capacity, budget, alerting, runbooks, service ownership, status-page dependency, deployment canary, stop thresholds, and tested rollback.
6. Record each gate as pass, fail, waived-by-owner with expiry, or not applicable; issue go only when blockers are resolved by named authorities.

## 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

Release, product, operations, security, privacy/data, and budget owners sign their scopes. A waiver names owner, risk, compensating control, expiry, and follow-up; this skill cannot self-approve.

## Error Handling

- Missing evidence is a failed or unresolved gate, not an assumed pass.
- Do not reuse a testnet or staging receipt as production environment evidence.
- Do not approve if rollback, key rotation, partial-response UX, or provider-unavailable behavior is untested.

## Output

Return the frozen release/environment manifest, gate matrix with evidence links, current-contract review, owner sign-offs, waivers, blockers, go/no-go decision, monitoring window, and rollback receipt. Mark assumptions, observations, source dates, environment-specific behavior, owners, and unresolved gaps explicitly.

## Examples

- Issue no-go when the release passes connectivity but has no explicit handling for a Portfolio HTTP 200 partial failure.
- Issue conditional go only when an authorized, expiring waiver identifies its control and does not bypass a non-waivable security boundary.

## Validation

Exercise and record expected and observed results for:

- wrong artifact SHA
- staging evidence substituted
- rotation failure
- provider outage
- budget alert
- rollback exercise

## Resources

- [Current first-party evidence map](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/alchemy-prod-checklist/references/official-docs.md) — recheck dated Alchemy sources before execution.
- Treat observed account, application, network, indexer, chain, or provider behavior as environment-specific evidence, never a universal guarantee.
