{"version":"2.1.275","anchor":"skillcommand-execution-now-restricted-to-composer-or-bridge","canonical_anchor":"skillcommand-execution-now-restricted-to-composer-or-bridge","heading":"Skill\/command execution now restricted to composer or bridge message origins","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/skillcommand-execution-now-restricted-to-composer-or-bridge","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Skill\/command execution now restricted to composer or bridge message origins\n\nSkills and slash commands now only run when triggered from the composer or a bridge message\n\n**Unclear.** The finding does not say what other origins previously could trigger execution or what the placeholder text says.\n\n**What**\n\nRunning a command (`command.run`) or a skill (`skill.prompt`) now checks where the request came from. It only actually executes if it originates from the composer (the message input box) or a bridge message; otherwise it returns a placeholder message instead of running.\n\n**Why**\n\nThis restricts skill and command execution to trusted origins, preventing them from being triggered from other, less expected sources.\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}