4 ms·
I haven't had much luck with skills being called appropriately. When I have a skill called "X doer", and then I write a prompt like "Open <file> and do X", it a
by esperent 11mo ago
I haven't had much luck with skills being called appropriately. When I have a skill called "X doer", and then I write a prompt like "Open <file> and do X", it almost never loads up the skill. I have to rewrite the prompt as "Open <file> and do X using the X doer skill".
Which is basically exactly as much effort as what I was doing previously of having prewritten sub-prompts/agents in files and loading up the file each time I want to use it.
I don't think this is an issue with how I'm writing skills, because it includes skill like the Skill Creator from Anthropic.
- slhck 11mo agoSame experience here – it seems I have to specifically tell it to use the "X skill" to trigger it reliably. I guess with all the different rules set up for Claude to follow, it needs that particular word to draw its attention to the required skill.
- _joel 11mo agoDitto, I also find it'll invariably decide to disregard the CLAUDE.md again and produce a load of crap I didn't really ask it for.
- notpublic 11mo agoTry adding a session hook that triggers on startup|resume|clear|compact to remind Claude about your custom skills.
- esperent 11mo agoIs there a session start hook? I don't think so, unless it was added recently. I've mostly been working on smaller projects so I never need to compact. And skills are definitely not working even on the initial prompt of a new session.