skills.rest
malinskibeniamin
malinskibeniaminCOMMUNITY
Explore all skills by this author →
GitHub

hook-audit

Analyze CLAUDE hook effectiveness from JSON metrics and generate a structured report.

3|1|Updated Mar 23, 2026
Search Tags:#analytics#audit#metrics#claude#reporting#session#hook
One-click install
npx skills add https://github.com/malinskibeniamin/skills --skill hook-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hook-audit
Source: https://github.com/malinskibeniamin/skills/tree/main/hook-audit
Command: npx skills add https://github.com/malinskibeniamin/skills --skill hook-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and quantify how CLAUDE hooks behave across sessions, surfacing silent, over-aggressive, and under-enforced hooks to inform improvements and team retrospectives.

Core Features & Use Cases

  • Analyze hook effectiveness across all session metrics.
  • Generate a retro-style analytics report for teams on recent sessions.
  • Detect silent or overly strict hooks and propose actionable adjustments.

Quick Start

Run hook-audit to generate a comprehensive report from your local hook metrics.

Frequently Asked Questions about hook-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Claude hook performance across recent sessions?▼

Run hook-audit to analyze hook effectiveness across all session metrics by reading JSON metrics from ~/.claude/hook-metrics and outputting a structured report. It surfaces silent, over-aggressive, and under-enforced hooks to inform improvements and retrospectives.

What is hook effectiveness analysis and when do I need it?▼

Hook effectiveness analysis quantifies how CLAUDE hooks behave across sessions to identify silent or overly strict hooks. You need it when preparing team retrospectives or evaluating whether your hooks are enforcing rules at the right level of strictness.

How do I generate a retro analytics report for Claude session metrics?▼

Generate a retro analytics report by running hook-audit, which reads local JSON metrics from ~/.claude/hook-metrics and produces a structured report on recent sessions. The report proposes actionable adjustments for detected silent or over-enforced hooks.

Do I need any dependencies or external tools to analyze hook metrics?▼

No external dependencies are required to analyze hook metrics. The Skill reads JSON metrics locally from the ~/.claude/hook-metrics directory and outputs a structured report without needing additional components or libraries installed.

Why are my Claude hooks not triggering during sessions?▼

Silent hooks that fail to trigger are detected by analyzing session metrics from ~/.claude/hook-metrics. The audit report identifies under-enforced hooks and proposes actionable adjustments so you can correct enforcement gaps in your configuration.

Can I use hook-audit for team retrospective analytics across multiple sessions?▼

Yes, hook-audit generates a retro-style analytics report for teams by analyzing session metrics across recent sessions. It reads local JSON metrics and surfaces hook behavior patterns to inform team retrospectives and configuration improvements.

Related Skills

Explore More Software Engineering Skills→
redpanda-dataredpanda-data
34

hook-audit

Analyze Claude Code hook performance metrics and detect silent or over-aggressive hooks.

Official
Advanced
bizzybaebizzybae

retro

Analyze commits, PR activity, and code quality metrics to generate weekly engineering retrospectives.

Community
Advanced
InnerScopeHearingInnerScopeHearing

fleet-telemetry

Capture Claude Code session metrics and forward them to PostHog.

Official
Advanced
flonatflonat
127

context-status

Diagnose Claude session health by analyzing local state files and modification times.

Community
Intermediate