One thing you'll note when defining custom
skills is that you'll end up with a bunch of new
slash commands. In Cloud Code, when you type a forward
slash in that command prompt here, you got a couple of
built-in and also custom slash commands to choose from.
The idea behind all the commands you see here, no matter if they're
custom or built-in, is that they give you quick access to
certain extra features and you already saw some built-in commands
like the init command already, for example.
The config command allows you to view and tweak the
configuration, the clear command clears the context,
that. But your skills will also show up as
commands here. For example, I got a modern, accessible HTML
JSX command in there because I got an equally named
skill in this project. But what's the idea behind
that? Well, the primary use case of these
skills is that Cloud Code can discover and use them
as needed depending on the task it's working on.
So the primary use case of these skills is not that you
invoke them, but you could invoke them.
You could invoke your skills as commands, but of course, it
will then depend on what's inside the skill
definition Markdown document what will happen.
And if it's just a bunch of extra knowledge like with the skills I
shared with you, nothing will really happen.
If I execute this bun instead of node skill here,
you'll see that Cloud Code starts working, but
it'll get back to me that it doesn't really know what to
do, because in that skill, I just share some general
knowledge about bun and that we're using bun instead of
Node.js, for example, but I don't tell it what to
do. However, you could, of course, build skills
that do have extra instructions or maybe even scripts
attached to them. That is something you can do, and in such
situations, you might occasionally wanna invoke them
commands. That's why this feature exists here.
However, the primary use case of skills is that
Cloud discovers and uses them and will later dive
into building custom commands that are primarily meant for execution
by you instead.