{"version":"2.1.91","anchor":"disable-shell-execution-in-skills-policy-setting","canonical_anchor":"disable-shell-execution-in-skills-policy-setting","heading":"Disable Shell Execution in Skills (Policy Setting)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.91\/e\/disable-shell-execution-in-skills-policy-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.91","markdown":"### Disable Shell Execution in Skills (Policy Setting)\n\n**What**\n\nA new `disableSkillShellExecution` policy\/config setting that prevents inline shell execution in skills and custom slash commands from user, project, or plugin sources.\n\nUsage: Set in your settings or policy configuration:\n\n`{ \"disableSkillShellExecution\": true }` **Details** - When enabled, shell command blocks (`` ```! `` fenced blocks and `` !`...` `` inline syntax) in skills are replaced with `[shell command execution disabled by policy]` - Applies to commands from user, project, or plugin sources \u2014 not policy settings - Useful for organizations that want to allow skills but prevent arbitrary shell execution **Evidence** Policy gate and replacement logic (search for `\"disableSkillShellExecution\"` and `\"[shell command execution disabled by policy]\"`)"}