Alchemy Infra
Change, plan, deploy, or debug infrastructure declared with Alchemy (v2) and secrets from Infisical. Use for alchemy stack edits, bindings, Durable Object classes, D1 or other migrations, custom domains, local Docker stacks, adding or rotating a Worker secret, secret drift between Infisical, CI, and the Worker, deploy failures, or rollback.
Install
npx skills add jpoehnelt/skills --skill alchemy-infragit clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/alchemy-infra ~/.claude/skills/alchemy-infraPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Infrastructure with Alchemy Alchemy programs are the only place infrastructure is declared. Never hand-edit generated deployment manifests, add Wrangler config, or change a stack-owned resource in a dashboard. Repo facts (from AGENTS.md): each stack's program file, stage names and which stage is production, plan, deploy, and local-run commands, the pinned Alchemy version and required Node version, where Alchemy state lives, the secret-name list in each stack, the Infisical environment and path per stage, the CI deploy jobs, and smoke-test commands. ## Stacks - List every stack before changing one: program file, stage, plan and deploy commands, local command. Local and remote stacks often share one set of service declarations; change the shared declaration so every stack picks it up, and keep stack files to names, ports, volumes, and secrets. - Alchemy v2 betas move quickly. Keep the exact version pin and check the Node version it needs before running it (type stripping of the program file needs a recent Node). - Know where state lives. Remote state for production means local runs cannot accidentally fork it; local `.alchemy/` state is disposable. Only the production stage should touch production, and production resources should be retained on removal. - Local ports come from the local stack's output or its instance registry; never hard-code them. ## Change a stack
Details
- Skill name
alchemy-infra- Repository
- jpoehnelt/skills
- Path
alchemy-infra/SKILL.md- License
- MIT
- Repo updated
- 12 November 2026
FAQ
What does the Alchemy Infra skill do?
Change, plan, deploy, or debug infrastructure declared with Alchemy (v2) and secrets from Infisical. Use for alchemy stack edits, bindings, Durable Object classes, D1 or other migrations, custom domains, local Docker stacks, adding or rotating a Worker secret, secret drift between Infisical, CI, and the Worker, deploy failures, or rollback.
How do I install the Alchemy Infra skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill alchemy-infra. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Alchemy Infra popular?
It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.
Related skills
Agents Correct
23jpoehnelt/skills
Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.
Agents Create Verification Skill
23jpoehnelt/skills
Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.
Agents Reflect
23jpoehnelt/skills
After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.
Effect Seam Migration
23jpoehnelt/skills
Move heavy or long-running work off a constrained runtime (for example the Cloudflare Workers memory or CPU ceiling) by first extracting domain logic into packages as Effect programs, then moving execution. Use when starting or continuing a runtime migration or moving a service across app boundaries.
Mastering AWS CLI
9SpillwaveSolutions/mastering-aws-cli
AWS CLI v2 quick-reference for experienced developers. Covers compute (Lambda, ECS, EKS), storage (S3, DynamoDB, Aurora), networking (VPC, SSM tunneling), security (IAM, Secrets Manager), and GitHub Actions CI/CD. Use when asked to "write aws commands", "debug aws access", "set up cross-account roles", "configure aws cli", "assume role", "S3 bucket operations", or "deploy to ECS".
Gcd
9rochacbruno/gcd-claude-skill
Google Cloud Dedicated (GCD) and Cloud de Confiance (S3NS) sovereign cloud expert. Use when working with sovereign Google Cloud regions, or when the user mentions GCD, Google Cloud Dedicated, Cloud de Confiance, S3NS, sovereign cloud, universe domain, apis-berlin-build0.goog, s3nsapis.fr, u-germany-northeast1, u-france-east1, Trusted Partner Cloud, TPC, or data sovereignty requirements for Google Cloud workloads. Provides guidance on region-specific services, authentication, Terraform, networking, and key differences from public Google Cloud. Also use when asked to review a PR, code review, or
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.