{"version":"2.1.304","anchor":"skill-hooks-can-run-via-runskillhook-skill-listing-includes","canonical_anchor":"skill-hooks-can-run-via-runskillhook-skill-listing-includes","heading":"Remote control can run a skill's hooks and list your own skills","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/skill-hooks-can-run-via-runskillhook-skill-listing-includes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Remote control can run a skill's hooks and list your own skills\n\nRemote-control clients can now run a skill's command hooks, unless settings keep them off, and see skills from your user settings\n\n**What**\n\nA skill is a packaged set of instructions Claude can use, and a hook is a command that runs automatically at a set moment. A program controlling Claude Code remotely can now ask it to run a skill's command hooks. Claude Code refuses if this machine's settings keep skill hooks turned off.\n\nThe list of skills and commands such a program can request now includes skills from your user settings, marked as coming from there, and not only those from the project. Each skill's details can also include the plugin it came from and its path on disk.\n\n**Why**\n\nApps that drive Claude Code remotely can now see and run more of your skills, while a machine set to keep skill hooks off still stays that way.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}