Skills claude-hooks
📦

claude-hooks

v1.0.1 Content revision r1 Safe 📁 Filesystem access⚙️ External commands

Configure Claude Code Hooks

Claude Code hooks are powerful but easy to misconfigure. This skill helps design validation, logging, notification, and cleanup hooks with clear event patterns.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "claude-hooks" from https://skillstore.io/skills/89jobrien-claude-hooks.md and its manifest at https://skillstore.io/api/skills/89jobrien-claude-hooks/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/89jobrien-claude-hooks.md Signed manifest GET /api/skills/89jobrien-claude-hooks/manifest Signed lockfile GET /api/skills/89jobrien-claude-hooks/lockfile

Test it

Using "claude-hooks". I need a hook that checks Bash commands before they run.

Expected outcome:

A concise PreToolUse plan with the Bash matcher, validation goal, command review points, and testing checklist.

Using "claude-hooks". I want to log file edits from Claude Code.

Expected outcome:

A PostToolUse logging approach that records local file paths only, notes privacy risks, and suggests log rotation.

Using "claude-hooks". I want a notification after Claude finishes work.

Expected outcome:

A Stop event notification plan with platform notes, quick execution guidance, and failure-handling recommendations.

Security Audit

Safe
v7 • 7/5/2026 Open versioned report

All ten static findings were adjudicated as false positives. The flagged backticks are Markdown formatting, the hidden path references document Claude Code configuration or local example logging, and the reconnaissance alerts match benign logging guidance. No prompt injection, network exfiltration, or malicious hook intent was found in the reviewed files.

2
Files scanned
203
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

📁 Filesystem access (6)
references/claude-hook.template.md:17 references/claude-hook.template.md:81 references/claude-hook.template.md:17 references/claude-hook.template.md:81 SKILL.md:48 SKILL.md:48
⚙️ External commands (2)
SKILL.md:35 SKILL.md:48
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/89jobrien-claude-hooks/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/89jobrien-claude-hooks/security.svg)](https://skillstore.io/skills/89jobrien-claude-hooks?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/89jobrien-claude-hooks?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/89jobrien-claude-hooks/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/89jobrien-claude-hooks.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

Joseph OBrien. (2026). claude-hooks security audit report (audit version 7) [Author version 1.0.1]. Skillstore. https://skillstore.io/skills/89jobrien-claude-hooks/audits/7

BibTeX citation

@techreport{joseph-obrien-89jobrien-claude-hooks-2026, author = {Joseph OBrien}, title = {claude-hooks security audit report (audit version 7)}, institution = {Skillstore}, year = {2026}, number = {7}, url = {https://skillstore.io/skills/89jobrien-claude-hooks/audits/7}, note = {Author version 1.0.1} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "claude-hooks security audit report (audit version 7)" version: "1.0.1" type: report authors: - name: "Joseph OBrien" date-released: "2026-07-05" url: "https://skillstore.io/skills/89jobrien-claude-hooks/audits/7" identifiers: - type: other value: "skillstore:89jobrien-claude-hooks:audit:7" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
41
Architecture
100
Maintainability
87
Content
71
Community
91
Spec Compliance

What You Can Build

Add Command Guardrails

Create PreToolUse hooks that check tool use before execution and explain the matcher strategy.

Create Local Audit Logs

Design PostToolUse logging for selected file events while keeping log scope clear and controlled.

Build Development Notifications

Configure notification or stop-event hooks that alert developers without interrupting normal Claude Code work.

Try These Prompts

Create a Basic Hook 
Help me create a Claude Code hook for one event. Ask me which event, matcher, and local command I want before drafting it.
Add Tool Validation 
Design a PreToolUse hook that warns before risky Bash commands. Explain the matcher choice and include testing steps.
Configure Local Logging 
Create a PostToolUse logging hook for file writes. Keep the log local, avoid secret data, and explain the privacy tradeoffs.
Review a Hook Policy 
Audit my planned Claude Code hook set for command safety, matcher scope, error handling, and noisy output. Recommend safer alternatives.

Best Practices

  • Keep hook commands fast and fail gracefully so automation does not interrupt Claude Code.
  • Use the narrowest matcher that covers the intended tool or command pattern.
  • Review logging and environment variable use for secrets before enabling a hook.

Avoid

  • Using a wildcard matcher when a specific tool matcher is enough.
  • Logging complete tool inputs or outputs without reviewing sensitive data exposure.
  • Running complex or long-lived shell commands directly inside synchronous hooks.

Frequently Asked Questions

Does this skill install hooks automatically?
No. It provides templates and guidance for configuring Claude Code hooks.
Which Claude Code events does it cover?
It covers PreToolUse, PostToolUse, Notification, and Stop events.
Can I use it with Codex?
Yes. Codex can use the guidance to reason about Claude Code hook configuration.
Does it support security validation hooks?
Yes. It can help design PreToolUse validation and blocking patterns.
Does it send data over the network?
The reviewed skill content does not include network calls or external data transfers.
What should I review before enabling a hook?
Review the matcher, shell command, environment variables, log destination, and failure behavior.

Developer Details

License

MIT

Author version

v1.0.1

Skillstore revision

r1

Repository

https://github.com/89jobrien/steve/tree/main/steve/skills/claude-hooks

Ref

c4037264bbd363c572662d6154a3ab28f5ca4f53

Maintenance freshness

7/18/2026

Usage

9 downloads · 241 views

File structure

📁 references/

📄 claude-hook.template.md

📄 SKILL.md