How do I advertise /grill-me after the refactor since it references /grilling?

[blmille1]

Everyone I share the /grill-me skill with loves it!
But I did notice a recent refactor where /grill-me (not auto-invokable) now references /grilling (auto-invokable) and so now I'm trying to reference it to my friends and coworkers with /grill-me (because the whole internet knows it as that), but then having to mention the refactor and to look at the /grilling skill.

So what's the most efficient way to both refer to it by the name everyone else on the internet knows it as (/grill-me), but also get them to /grilling?

For those whom I can drop a link it, this is a mute point. But most of the time I'm advertising it by word of mouth.
And many of those are non-devs but can work their way around ChatGPT and just need a copy/paste.
I know, I know--chatbot. But it's a great skill even for chatbots and everyone who uses it changes their workflow.

Also, how do you handle skill dependencies? It appears (maybe I'm wrong) that skills have no formal dependency resolution. When you install a skill with dependencies, you have to make sure you install all of them.

It would be nice if there were a format that would handle that for you like NPM.
Your thoughts?

P.S.:
@mattpocock I love your videos and I've been steeped in your skills and sandcastle for the last two weeks. Thank you so much for all of your wonderful content!

[VectorPeak]

For word of mouth, I’d keep advertising it as /grill-me. That’s the user-facing name. /grilling is more like the reusable implementation/detail underneath it.

The shortest copy/paste version I’d give people is:

Install both skills: /grill-me and /grilling.
Then start with: /grill-me

On dependencies: you’re reading it right. There isn’t formal dependency resolution for skills at the moment, so if one skill references another, both need to be installed manually. An npm-style manifest would be a good direction here, something like:

{
 "name": "grill-me",
 "dependencies": ["grilling"]
}

Then installers/tools could resolve that automatically. Until something like that exists, the practical answer is to treat /grill-me as the thing you tell people to run, and mention /grilling only as a required install alongside it.

---

如果我的回答解决了您的问题，您可以点一下 answered the question，其实我是来解答问题，顺带着收集 Galaxy Brain 徽章的哈哈 😆