claude-code - 💡(How to fix) Fix [Bug] Skill call used hook not triggered for command execution [1 comments, 2 participants]

TL;DR

The issue may be resolved by modifying the command execution to trigger the skill call used hook, potentially through changes in the integration or hook configuration.

Guidance

• Review the current implementation of the skill call used hook to understand the conditions under which it is triggered, and compare this to the execution of the /my-skill-name command.
• Investigate if there are any specific settings or configurations in the version 2.1.97 of the platform that could be influencing the hook's behavior, especially considering the darwin platform and ghostty terminal.
• Consider testing the command execution and hook triggering in a different environment or version to isolate if the issue is specific to the current setup.
• Examine the documentation or support resources for the platform to see if there are known issues or workarounds related to skill usage metrics and hook triggering.

Notes

The provided information does not specify the exact technical details of the hook or the command execution, which limits the ability to provide a precise fix. Further investigation into the platform's documentation and the specific configurations of the environment in question is necessary.

Recommendation

Apply workaround: Given the inconsistency in the current implementation and the lack of information on a fixed version that addresses this issue, applying a workaround such as manually triggering the skill call used hook when the /my-skill-name command is executed might be the most feasible approach.