tool-hooks-doctor

Claude Code evolution hooks may not be generating output because the underlying hook scripts are missing from `~/.claude/skills/skill-evolution/hooks/` or their configuration is absent from project and global settings. This Skill diagnoses both conditions and reports the status as OK, PARTIAL, or MISSING.

To check if Claude Code hooks are installed and enabled, run this diagnostic Skill to verify the presence of hook scripts in the local skills directory and confirm their enablement within your project or global settings file, providing an immediate status report.

Yes, you can automatically fix missing Claude Code hook configurations. After diagnosing the installation status, this Skill offers an automated fix that installs the necessary project-level hooks by executing a Python script, subject to your explicit confirmation.

A PARTIAL status when diagnosing Claude Code hook issues means that either the hook scripts exist in the designated directory but lack proper enablement in settings, or the settings are configured but the corresponding hook script files are missing.

Yes, you need Python installed in your environment to apply the automated fix. The Skill utilizes a Python script to install the necessary project-level evolution hooks when the diagnostic report indicates they are missing or incorrectly configured.

Claude Code hook settings directly control skill evolution by triggering scripts that generate evolution artifacts after a task runs. If these settings are missing or the hook scripts are uninstalled, the expected output will not appear in the `runs/evolution` directory.