CLAUDE_CODE_SKILL_PROPOSALS
A Claude Code environment variable, read out of the shipped bundle. It has been in the build since v2.1.233, including the newest one read.
An env var turns on the tool that proposes new skills; otherwise it stays off in this build.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.233.
In the changelogs
6Releases whose published page names CLAUDE_CODE_SKILL_PROPOSALS.
-
v2.1.290
Several small changes to skills, file lists, sign-in and error handling
A set of small changes covering skill proposals, synced file paths, sign-in retries, config file lists, scheduled tasks and telemetry
found in this entry's text
-
v2.1.259
New env vars added to allowlists/passthrough
Several environment variables were added to passthrough allowlists, including GIT_ALLOW_PROTOCOL and CLAUDE_CODE_SKILL_PROPOSALS.
found in this entry's text, named in this entry
-
v2.1.259
Skill-proposal tool gating tightened, still cloud/remote-only
The skill-proposal tool now requires a remote environment and a specific entrypoint or env var, and can be vetoed per session.
found in this entry's text, named in this entry
-
v2.1.251
Skill proposals no longer behind a remote flag
Skill proposals no longer need a server flag; two environment variables now decide.
named in this entry, found in this entry's text
-
v2.1.233
CLAUDE_CODE_SKILL_PROPOSALSturns on the skill-proposal toolAn env var turns on the tool that proposes new skills; otherwise it stays off in this build.
named in this entry, found in this entry's text
-
v2.1.233
Two more variables recognised when building subprocess environments
Two more Claude-owned variables are handled when building environments for subprocesses.
named in this entry, found in this entry's text
First cited
1The earliest release whose published evidence quoted CLAUDE_CODE_SKILL_PROPOSALS was v2.1.233, 14 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
66One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.