mcpbeat

Claude Hooks

aiskillstore/claude-hooks

Claude Code hooks configuration specialist. Use when creating hooks for tool validation, logging, notifications, or custom automation in Claude Code.

This is a copy. The original lives at comeonoliver/claude-hooks.

5k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
404
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/aiskillstore/marketplace --skill claude-hooks

What comes with it

19 948 bytes besides the instruction
references/claude-hook.template.md
skill-report.json

The instruction itself

7 sections, as written by the author

Claude Hooks Skill

Creates and configures hooks for Claude Code to automate workflows and extend functionality.

What This Skill Does

  • Creates PreToolUse validation hooks
  • Sets up PostToolUse logging/cleanup
  • Configures notification hooks
  • Implements custom automation
  • Documents hook patterns

When to Use

  • Tool execution validation
  • Audit logging
  • Custom notifications
  • Workflow automation
  • Security controls

Reference Files

  • references/CLAUDE_HOOK.template.md - Hook configuration examples and patterns

Hook Events

| Event | Trigger | Use Case |

|-------|---------|----------|

| PreToolUse | Before tool executes | Validation, blocking |

| PostToolUse | After tool completes | Logging, cleanup |

| Notification | Claude sends notification | Alerts |

| Stop | Claude stops | Final reports |

Configuration Location

Hooks are configured in ~/.claude/settings.json under the hooks key.

Best Practices

  • Keep hooks fast (< 1 second)
  • Handle errors gracefully
  • Use specific matchers
  • Test hooks independently
  • Avoid verbose output

How to use it

Copy the folder

Take aiskillstore/claude-hooks from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.