Have you tried analysing all your prompts, and then telling it to "figure out" what custom skills might improve your prompts?
I do actually have another project I'm working on that does this... it's been super useful for seeing how I prompt, what Skills I use and getting them to evolve and improve (I know Hermes does some of this, but it's been interesting rolling my own - will release soon!!)
replyYou can use edit your settings.json in ~/.claude and put a hook for it like this:
reply "Stop": [
{
"hooks": [
{
"type": "command",
"command": "afplay ~/.claude/hooks/chime.wav",
"async": true
},That hook is also called when subagents stop which means you'll get a lot of false positives.
replyIdeally you are only notified when the main agent stops, the main agent has a question, or a subagent has a question.
I created a script that figures out if any of those states apply before emitting a macOS notification and then called it in each hook:
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "script.sh",
"timeout": 10
}
]
}
],
"PreToolUse": ...
"PermissionRequest": ...
"Elicitation": ...Try superset, it does that
replyCmux notifications does this too
reply