Yeah, after reading this I was thinking, "how is this different from agents using a combination of tools, resources, and prompts?" They do surprising things sometimes but it's not particularly novel of Claude Code.
My big gripe with skills is getting claude webapp and claude code to get them to invoke them in the right situations (often unexpected situations) without explicitly telling it directly to use skill x + skill y.
Ideally I would build a bunch of atomic skills that combine well and claude just uses them naturally when the situation arises.
Regardless of title, it’s a good little reminder that I hadn’t thought of - skills can use skills. This makes sense - a skill is just a pre-loaded context Claude instance, so why not? But I also tend to think of one skill at a time. Thanks for the write up.
You can make a router skill that describes how to use the other skills together. I'm experimenting with this now but my core problem is still How to Make Claude Code Skills Activate Reliably.
During testing today I asked a task I knew should have activated a skill and claude just did it without the skill instead.
The activation reliability issue kingkongjaffa mentions is the real challenge here. It's the same problem you hit building any pattern-based system - getting it to recognise when a pattern applies vs when it should improvise.
I've been building transaction categorisation tools and the parallel is striking. You can have perfect pattern logic, but the model still needs to correctly identify "this situation matches pattern X" first. Sometimes it just... doesn't, even when it clearly should.
The router skill idea is interesting. Feels like pushing the meta-matching problem up a level though - now you need the router to activate reliably. Turtles all the way down.
I wonder how complex we can make skills if claude code was able to read them dynamically. I am envisioning one session generates the skill.md while other session works on it and then I envision they both editing each other's skill.md. just a little dream I have, sorry for yapping.
That's what I have been doing as I'm building these skills out. There is a really fun testing/tdd loop that runs these skills through multiple prompts with baselines and tests it all out.
Getting a 404 Not Found for this post - is the blog down?
I was really curious to read it given the comments + full disclosure my co-founder recently wrote about a similar topic ("To Tool or Not to Tool") https://blog.codeyam.com/p/to-tool-or-not-to-tool .
I wanted to see how this is similar or different with the focus on Claude Code + Skills in a more literal sense vs. tools in a more abstract sense.
fooqux|1 month ago
joshribakoff|1 month ago
oooyay|1 month ago
ryanthedev|1 month ago
kingkongjaffa|1 month ago
Ideally I would build a bunch of atomic skills that combine well and claude just uses them naturally when the situation arises.
ryanthedev|1 month ago
At some point I plan to do some ralph wiggum loop stuff maybe to hash out the best way for triggers to work.
vessenes|1 month ago
kingkongjaffa|1 month ago
During testing today I asked a task I knew should have activated a skill and claude just did it without the skill instead.
This might help: https://scottspence.com/posts/how-to-make-claude-code-skills...
NamlchakKhandro|1 month ago
That's it
ryanthedev|1 month ago
jackfranklyn|1 month ago
I've been building transaction categorisation tools and the parallel is striking. You can have perfect pattern logic, but the model still needs to correctly identify "this situation matches pattern X" first. Sometimes it just... doesn't, even when it clearly should.
The router skill idea is interesting. Feels like pushing the meta-matching problem up a level though - now you need the router to activate reliably. Turtles all the way down.
ryanthedev|1 month ago
It's really going to be interesting to see how this tech evolves.
d4rkp4ttern|1 month ago
E.g. you could have:
- a set of skills to use design patterns of a library
- a skill to add to this skill-set -- either when prompted by user or autonomously via a stop-hook
E.g. I set up this combination for design patterns for the Langroid[1] LLM-Agent framework:
https://github.com/pchalasani/claude-code-tools/tree/main/pl...
[1] https://github.com/langroid/langroid
joshribakoff|1 month ago
amatecha|1 month ago
ryanthedev|1 month ago
falloutx|1 month ago
ryanthedev|1 month ago
That's what I have been doing as I'm building these skills out. There is a really fun testing/tdd loop that runs these skills through multiple prompts with baselines and tests it all out.
nadis|1 month ago
I was really curious to read it given the comments + full disclosure my co-founder recently wrote about a similar topic ("To Tool or Not to Tool") https://blog.codeyam.com/p/to-tool-or-not-to-tool .
I wanted to see how this is similar or different with the focus on Claude Code + Skills in a more literal sense vs. tools in a more abstract sense.
unknown|1 month ago
[deleted]
rafaquintanilha|1 month ago
unknown|1 month ago
[deleted]
ryanthedev|1 month ago
ironbound|1 month ago
mkw5053|1 month ago
unknown|1 month ago
[deleted]
unknown|1 month ago
[deleted]
_joel|1 month ago
miquong|1 month ago
(year fixed below)