Agent skill

Alchemy Env Types

Derive Cloudflare worker env types from Alchemy resource Env types instead of hand-writing env shapes.

LGPL-3.0Auto-check passed

Install Alchemy Env Types

skills CLI

$ npx skills add Consensys/c0 --skill alchemy-env-types -a claude-code

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

GitHub CLI

$ gh skill install Consensys/c0 alchemy-env-types --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/Consensys/c0.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/alchemy-env-types .claude/skills/alchemy-env-types && 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/

Paste into Claude Code

Install the "alchemy-env-types" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/alchemy-env-types into .claude/skills/alchemy-env-types/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alchemy-env-types", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Consensys/c0/tree/master/.agents/skills/alchemy-env-types

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Consensys/c0 --skill alchemy-env-types -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Consensys/c0 alchemy-env-types --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/alchemy-env-types .agents/skills/alchemy-env-types && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "alchemy-env-types" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/alchemy-env-types into .agents/skills/alchemy-env-types/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alchemy-env-types", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Consensys/c0 --skill alchemy-env-types -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Consensys/c0 alchemy-env-types --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/alchemy-env-types .cursor/skills/alchemy-env-types && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "alchemy-env-types" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/alchemy-env-types into .cursor/skills/alchemy-env-types/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alchemy-env-types", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Consensys/c0.git --path .agents/skills/alchemy-env-types

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Consensys/c0 --skill alchemy-env-types -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Consensys/c0 alchemy-env-types --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/alchemy-env-types .gemini/skills/alchemy-env-types && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "alchemy-env-types" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/alchemy-env-types into .gemini/skills/alchemy-env-types/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alchemy-env-types", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Consensys/c0 alchemy-env-types

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Consensys/c0 --skill alchemy-env-types -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/alchemy-env-types .github/skills/alchemy-env-types && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "alchemy-env-types" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/alchemy-env-types into .github/skills/alchemy-env-types/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alchemy-env-types", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Consensys/c0 --skill alchemy-env-types -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Consensys/c0 alchemy-env-types --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/alchemy-env-types .opencode/skills/alchemy-env-types && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "alchemy-env-types" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/alchemy-env-types into .opencode/skills/alchemy-env-types/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alchemy-env-types", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: alchemy-env-types
GitHub stars: 105
Token cost: ~707 tokens
SKILL.md length: 255 words
Files: 1
Skills in repo: 11
Repo updated: Aug 18, 2026
First seen: Oct 7, 2026
Licence: LGPL-3.0

At a glance

Derive Cloudflare worker env types from Alchemy resource Env types instead of hand-writing env shapes.

Works in 4 steps: Export the worker resource type from infra → Derive an env alias from that resource… → In the app declaration file, extend… → …
Editing worker bindings
SKILL.md covers Pattern, Repo Notes, When Changing Bindings and Bad, plus 1 more section
Needs INTERNAL_CALLBACK_SECRET

What it does

Alchemy Env Types is an agent skill from Consensys/c0. Derive Cloudflare worker env types from Alchemy resource Env types instead of hand-writing env shapes. Use when editing worker bindings, adding or removing env vars in packages/infra, touching cloudflare-env.d.ts or env.d.ts files, importing from cloudflare:workers, or fixing env typing in API or web apps.

Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Cloudflare Workers and Cloudflare. The repository describes itself as: c0 is an open-source AI platform built for organizational work, tools, and context. A single deployment to Cloudflare to get started. The licence is LGPL-3.0.

When your agent uses it

Editing worker bindings
Removing env vars in packages/infra
Touching cloudflare-env.d.ts
Importing from cloudflare:workers

Example prompts

“/alchemy-env-types”

Requirements

A credential in INTERNAL_CALLBACK_SECRET

Workflow steps

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

Export the worker resource type from infra
Derive an env alias from that resource in packages/infra/src/types/
In the app declaration file, extend Cloudflare.Env from that alias
If the app imports env from cloudflare:workers, make sure the module is declared and exports that merged env type

What it can do on your machine

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

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
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 these keys or tokens, usually read from environment variables:
- INTERNAL_CALLBACK_SECRET
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Alchemy Env Types loads about 707 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 255 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~707

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 Consensys/c0 at commit e7a1810, republished under its LGPL-3.0 licence (© Consensys). 255 words, ~707 tokens.

Download SKILL.mdSave it as .claude/skills/alchemy-env-types/SKILL.md (or your agent's skills folder).

name: alchemy-env-types
description: Derive Cloudflare worker env types from Alchemy resource Env types instead of hand-writing env shapes. Use when editing worker bindings, adding or removing env vars in packages/infra, touching cloudflare-env.d.ts or env.d.ts files, importing from cloudflare:workers, or fixing env typing in API or web apps.

Alchemy Env Types

Use Alchemy's generated worker Env type as the single source of truth for Cloudflare env bindings in this repo.

Do not hand-write env shapes like Record<string, string | undefined>.
Do not redeclare individual env vars in app typing files when the Alchemy resource type already contains them.
Do not locally cast env in app code if the declaration file can carry the correct type.

Pattern

Export the worker resource type from infra:

export type WebResource = Awaited<ReturnType<typeof createWeb>>

Derive an env alias from that resource in packages/infra/src/types/:

import type { WebResource } from "../web"

export type WebEnv = WebResource["Env"]

In the app declaration file, extend Cloudflare.Env from that alias:

declare namespace Cloudflare {
  type WebEnv = import("infra/types/web-env").WebEnv
  interface Env extends WebEnv {}
}

If the app imports env from cloudflare:workers, make sure the module is declared and exports that merged env type:

interface CloudflareEnv extends Cloudflare.Env {}

declare module "cloudflare:workers" {
  export const env: CloudflareEnv
}

Repo Notes

apps/api/env.d.ts is the reference API pattern.
apps/web/cloudflare-env.d.ts is the reference web pattern.
packages/infra/src/types/env.ts contains API env aliases.
packages/infra/src/types/web-env.ts contains the web env alias.
In this repo, the web app needs the declare module "cloudflare:workers" block so TypeScript can resolve that module. Keep that block minimal and sourced from Cloudflare.Env.

When Changing Bindings

When adding, removing, or renaming a binding in infra:

Update the Alchemy resource definition in packages/infra/src/web.ts or the corresponding worker factory.
Make sure the worker resource type is exported.
Make sure the app declaration file extends the env alias derived from that worker resource.
Remove any manual env var redefinitions or local casts that duplicate the generated type.

Bad

const env = cloudflareEnv as {
  VITE_STAGE?: string
}

declare module "cloudflare:workers" {
  export const env: {
    VITE_STAGE: string
    INTERNAL_CALLBACK_SECRET: string
  }
}

Good

import { env } from "cloudflare:workers"

const stage = env.VITE_STAGE

Keep the declaration layer thin. The env var list should come from Alchemy, not be copied by hand into app code.

Files

Just SKILL.md in .agents/skills/alchemy-env-types of Consensys/c0.

Open the folder on GitHubat commit e7a1810

Compare with similar skills

Alchemy Env Types 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 Env Types compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Alchemy Env Types this skillConsensys/c0	105	—	~707	Automated safety check: Pass	LGPL-3.0	1 mo ago
Cloudflare Browser Renderingcloudflare/moltworker	9.9k	—	~742	Automated safety check: Pass	Apache-2.0	5 mo ago
Cloudflarehodgef/apiker	127	7 repos	~2.2k	Automated safety check: Pass	MIT	1 mo ago
Nextjs On Cloudflarecloudflare/skills	3k	2 repos	~678	Automated safety check: Pass	Apache-2.0	7 days ago
Agents SDKcloudflare/skills	3k	2 repos	~3k	Automated safety check: Pass	Apache-2.0	7 days ago
Cloudflaredmmulroy/cloudflare-skill	727	—	~1.6k	Automated safety check: Pass	MIT	8 mo ago

Similar skills

Cloudflare Browser Rendering
cloudflare/moltworker
Official
Drives headless Chrome through Cloudflare Browser Rendering over a CDP WebSocket to take screenshots, navigate and scrape pages, and record multi-page videos.
9.9k GitHub stars~742 tokensUpdated 5 mo ago
Productivity & AutomationAuto-check passed
Cloudflare
hodgef/apiker
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF…
127 GitHub starsUsed in 7 repos~2.2k tokens
DevOps & CloudAuto-check passed
Nextjs On Cloudflare
cloudflare/skills
Official
Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext.
3k GitHub starsUsed in 2 repos~678 tokens
DevOps & CloudAuto-check passed
Agents SDK
cloudflare/skills
Official
Build, debug, or review Cloudflare Agents SDK applications using the agents package.
3k GitHub starsUsed in 2 repos~3k tokens
Agent WorkflowsAuto-check passed
Cloudflare
dmmulroy/cloudflare-skill
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and…
727 GitHub stars~1.6k tokensUpdated 8 mo ago
DevOps & CloudAuto-check passed
Durable Objects
cloudflare/skills
Official
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
3k GitHub starsUsed in 2 repos~1.5k tokens
Backend & APIsAuto-check passed

Questions about Alchemy Env Types

What does Alchemy Env Types do?

Derive Cloudflare worker env types from Alchemy resource Env types instead of hand-writing env shapes. Alchemy Env Types is an agent skill from Consensys/c0. Derive Cloudflare worker env types from Alchemy resource Env types instead of hand-writing env shapes.

When should I use Alchemy Env Types?

Alchemy Env Types fits situations like: editing worker bindings; removing env vars in packages/infra; touching cloudflare-env.d.ts; importing from cloudflare:workers.

How do I install Alchemy Env Types in Claude Code?

Run `npx skills add Consensys/c0 --skill alchemy-env-types -a claude-code`. Or copy the skill folder (.agents/skills/alchemy-env-types in Consensys/c0) into .claude/skills/alchemy-env-types in your project. Claude Code loads it when a task matches its description.

How do I install Alchemy Env Types in Codex?

Run `npx skills add Consensys/c0 --skill alchemy-env-types -a codex`. Or copy the skill folder (.agents/skills/alchemy-env-types in Consensys/c0) into .agents/skills/alchemy-env-types in your project. Codex loads it when a task matches its description.

Can I use Alchemy Env Types 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 Consensys/c0 --skill alchemy-env-types -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-env-types, .gemini/skills/alchemy-env-types, .github/skills/alchemy-env-types and .opencode/skills/alchemy-env-types in your project.

What does Alchemy Env Types need to run?

Going by SKILL.md and its folder, Alchemy Env Types needs credentials named INTERNAL_CALLBACK_SECRET. Our summary lists: A credential in INTERNAL_CALLBACK_SECRET.

Does Alchemy Env Types 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 Env Types 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 Env Types use?

Alchemy Env Types is published under the LGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Alchemy Env Types use?

About 707 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Alchemy Env Types?

Skills that share tags, products or a category with Alchemy Env Types: Cloudflare Browser Rendering (cloudflare/moltworker, 9.9k stars), Cloudflare (hodgef/apiker, 127 stars), Nextjs On Cloudflare (cloudflare/skills, 3k stars) and Agents SDK (cloudflare/skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Alchemy Env Types?

Consensys (a GitHub organization) maintains it in Consensys/c0, which has 105 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 18, 2026.

Source: Consensys/c0 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Alchemy Env Types

Install Alchemy Env Types

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Alchemy Env Types

Pattern

Repo Notes

When Changing Bindings

Bad

Good

Files

Compare with similar skills

Similar skills

Cloudflare Browser Rendering

Cloudflare

Nextjs On Cloudflare

Agents SDK

Cloudflare

Durable Objects

More from Consensys/c0

Debug Cloudflare Workers Observability

Deslop Typescript

Implement Workflow Node

Workflow Runtime Abi

Agent Eval Loop

C0 Config

Questions about Alchemy Env Types

Install Alchemy Env Types

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Alchemy Env Types

Pattern

Repo Notes

When Changing Bindings

Bad

Good

Files

Compare with similar skills

Similar skills

More from Consensys/c0

Related

Questions about Alchemy Env Types