Mods, traditional hooks and skills

Mods: programs inside a session

Function hooks handle events and render interfaces. They suit live HUDs, tool behavior enhancements and interactive state. They require code and resource and permission management.

Traditional hooks: event-triggered scripts

Traditional hooks usually run a command or script after an event, for validation, notifications and automation. Permissions depend on the script and its environment.

Skills: reusable operating instructions

Skills give the model domain knowledge and steps for a workflow. They can work with mods, but documentation cannot replace program permission boundaries.

How to choose

If you only need to tell Claude how to work, consider a skill first. For a fixed step after an event, consider a traditional hook. For persistent displays or in-session interaction, consider a mod.

Start small. Avoid adding a whole background service for a simple reminder.