hook
Enable, disable, and manage Claude Code hooks. Use for hook debugging or configuration.
What this skill does
# Hook Management System Manage Claude Code hooks for the current session. ## When to use - When you need to check the status of Claude Code hooks - When you want to temporarily disable a noisy or problematic hook - When debugging hook behavior or performance issues - When monitoring hook execution metrics ## Usage ``` /hook status # Show all hooks and their status /hook list # List available hooks with descriptions /hook disable [hook-name] # Temporarily disable a hook /hook enable [hook-name] # Re-enable a disabled hook /hook profile # Show hook performance metrics /hook logs [hook-name] # View recent logs for a hook ``` ## Instructions When this command is invoked: ### /hook status 1. Read `~/.claude/settings.json` 2. Parse the hooks configuration 3. Check `~/.claude/hooks/.disabled` for disabled hooks 4. Display in a formatted table: - Hook type (SessionStart, PreToolUse, PostToolUse, and others) - Matcher pattern - Command/Prompt - Status (enabled/disabled) ### /hook list 1. Scan `~/.claude/hooks/` directory 2. List each hook file with: - Filename - Description (from docstring) - Trigger type - Last modified ### /hook disable [hook-name] 1. Create/update `~/.claude/hooks/.disabled` file 2. Add the hook name to the disabled list 3. Hooks check this file before running 4. Note: Changes persist until re-enabled ### /hook enable [hook-name] 1. Read `~/.claude/hooks/.disabled` file 2. Remove the hook name from the disabled list 3. Confirm the hook is re-enabled ### /hook profile 1. Read `~/.claude/logs/hook_metrics.jsonl` 2. Calculate average execution time per hook 3. Show: - Hook name - Avg execution time (ms) - Total calls - Success rate - Token impact estimate ### /hook logs [hook-name] 1. Find log files in `~/.claude/logs/` 2. Filter by hook name 3. Show last 20 entries 4. Include timestamp, result, and any errors ## Examples ```bash # Check current hook status /hook status # Disable noisy notifications temporarily /hook disable notification # Re-enable when ready /hook enable notification # Check performance impact /hook profile # Debug a specific hook /hook logs post_tool_use ``` ## Notes - Disabled state uses `~/.claude/hooks/.disabled` file - Performance data from `~/.claude/logs/hook_metrics.jsonl` - Hooks check disabled state before executing - Session-based disabling (resets on restart)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.