smithery.ai

claude-hooks

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

First seen Mar 23, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.1
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,375 B
  • docs SUMMARY.md 169 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

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