{"version":"2.1.259","anchor":"skill-proposal-tool-gating-tightened-still-cloudremote-onl","canonical_anchor":"skill-proposal-tool-gating-tightened-still-cloudremote-onl","heading":"Skill-proposal tool gating tightened, still cloud\/remote-only","tier":"soon","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/skill-proposal-tool-gating-tightened-still-cloudremote-onl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Skill-proposal tool gating tightened, still cloud\/remote-only\n\nThe skill-proposal tool now requires a remote environment and a specific entrypoint or env var, and can be vetoed per session.\n\nThe `isEnabled` gate for the skill-proposal tool (which proposes skills from recurring procedures for the user to review and save) is now stricter: it bails out for child sessions and nested Claude Code, requires `CLAUDE_CODE_REMOTE_ENVIRONMENT_TYPE` to be set, and only fires under the `remote_cowork` entrypoint or the `CLAUDE_CODE_SKILL_PROPOSALS` env var, with an additional per-session \"skills sync vetoed\" flag that can veto it.\n\n- Area: Skills\n- Names: `CLAUDE_CODE_SKILL_PROPOSALS`, `CLAUDE_CODE_REMOTE_ENVIRONMENT_TYPE`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}