ClaudeMods
☰
EN
● — online · Views — times
SponsorsSubmit a project
OUR GUIDES / LEARN · Updated Nov 18, 2026 · by ClaudeMods

Mods vs hooks vs skills vs MCP

Match the mechanism to the job

Several mechanisms can coexist in one workflow. Choose based on the behavior you need, then keep each component small enough to inspect.

MechanismMain purposeUseful exampleReview concern
ModEvent handlers and session UILive counter or paneCode, dependencies and permissions
Classic hookRun configured actions on eventsValidate a changeShell commands and exit behavior
SkillGive Claude a reusable procedureReview a releaseInstructions and tools it may invoke
MCPConnect a tool or data serviceQuery a remote catalogServer access and returned data

Compose without confusing responsibilities

A skill can explain when to use a tool exposed by an MCP server. A classic hook can perform a fixed check. A mod can display progress. None of these choices removes the need to authorize sensitive operations. Remote service text and repository content remain untrusted input.

A practical decision sequence

If the task is mainly instructions, write a skill. If it is a fixed action at an event, try a classic hook. If it needs session interaction or a persistent interface, examine a mod. If the missing capability lives in a separate service, examine MCP. Before switching mechanisms, list what state, credentials and failure handling the workflow actually needs.

Convert a classic hook · Create a starter

Guides