claude-code - 💡(How to fix) Fix Allow disabling built-in skills (e.g. `schedule`) via settings [1 comments, 2 participants]

TL;DR

To address the issue of the schedule skill being injected into the system prompt and consuming tokens, even when cloud agents are disabled, consider adding a settings key to disable named built-in skills.

Guidance

• Introduce a disabledBuiltinSkills key in both settings.json and managed-settings.json to allow users and organizations to opt out of specific skills.
• Set the value of disabledBuiltinSkills to an array containing the names of skills to be disabled, such as ["schedule"].
• Ensure that when a skill is disabled, its system-prompt sections are omitted and its associated slash commands and tools are unregistered.
• Review related issues, such as #52802 and PR #46024, to understand the broader context and potential overlaps with the proposed solution.

Example

{
  "disabledBuiltinSkills": ["schedule"]
}

Notes

The proposed solution focuses on adding a settings key to disable specific built-in skills. This approach may not address all aspects of skill injection and token consumption but provides a targeted way to opt out of the schedule skill.

Recommendation

Apply the workaround by introducing the disabledBuiltinSkills key in the settings files, as it directly addresses the issue of unnecessary token consumption by the schedule skill when cloud agents are disabled.