13 comments

[ 3.5 ms ] story [ 32.1 ms ] thread
I didn't see any emergent behavior, just combining of skills (which I'll admit looks useful). Calling this emergent is click bait.
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.
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.
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.

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.

Kiss of death? I'm seeing "404 Not Found nginx/1.18.0 (Ubuntu)"
No AI could code a better seahorse emoji xD
(comment deleted)