WEBVTT

00:00:00.120 --> 00:00:03.520
One thing you'll note when defining custom

00:00:03.760 --> 00:00:07.540
skills is that you'll end up with a bunch
of new

00:00:07.660 --> 00:00:11.220
slash commands. In Cloud Code,
when you type a forward

00:00:11.280 --> 00:00:14.940
slash in that command prompt here,
you got a couple of

00:00:15.060 --> 00:00:18.700
built-in and also custom slash commands to
choose from.

00:00:18.760 --> 00:00:22.380
The idea behind all the commands you see
here, no matter if they're

00:00:22.460 --> 00:00:26.410
custom or built-in, is
that they give you quick access to

00:00:26.460 --> 00:00:30.370
certain extra features
and you already saw some built-in commands

00:00:30.400 --> 00:00:33.260
like the init command already,
for example.

00:00:33.320 --> 00:00:36.260
The config command allows you to view
and tweak the

00:00:36.300 --> 00:00:40.160
configuration,
the clear command clears the context,

00:00:40.220 --> 00:00:43.840
that. But your skills will also show up as

00:00:43.880 --> 00:00:47.840
commands here. For example,
I got a modern, accessible HTML

00:00:47.980 --> 00:00:51.240
JSX command in there because I got an
equally named

00:00:51.300 --> 00:00:54.960
skill in this project.
But what's the idea behind

00:00:55.020 --> 00:00:58.160
that? Well, the primary use case of these

00:00:58.340 --> 00:01:02.160
skills is that Cloud Code can discover
and use them

00:01:02.180 --> 00:01:05.040
as needed depending on the task it's
working on.

00:01:05.080 --> 00:01:09.040
So the primary use case of these skills
is not that you

00:01:09.100 --> 00:01:12.710
invoke them, but you could invoke them.

00:01:12.760 --> 00:01:16.660
You could invoke your skills as commands,
but of course, it

00:01:16.700 --> 00:01:19.700
will then depend on what's inside the
skill

00:01:19.800 --> 00:01:22.940
definition Markdown document what will
happen.

00:01:22.950 --> 00:01:26.660
And if it's just a bunch of extra
knowledge like with the skills I

00:01:26.700 --> 00:01:30.160
shared with you,
nothing will really happen.

00:01:30.200 --> 00:01:34.160
If I execute this bun instead of node
skill here,

00:01:34.280 --> 00:01:38.160
you'll see that Cloud Code starts working,
but

00:01:38.240 --> 00:01:42.000
it'll get back to me
that it doesn't really know what to

00:01:42.080 --> 00:01:45.910
do, because in that skill,
I just share some general

00:01:45.980 --> 00:01:49.150
knowledge about bun and
that we're using bun instead of

00:01:49.200 --> 00:01:52.860
Node.js, for example,
but I don't tell it what to

00:01:52.900 --> 00:01:56.580
do. However, you could, of course,
build skills

00:01:56.660 --> 00:02:00.180
that do have extra instructions
or maybe even scripts

00:02:00.280 --> 00:02:03.340
attached to them. That
is something you can do, and in such

00:02:03.520 --> 00:02:07.460
situations,
you might occasionally wanna invoke them

00:02:07.520 --> 00:02:10.919
commands.
That's why this feature exists here.

00:02:10.940 --> 00:02:14.500
However, the primary use case of skills
is that

00:02:14.520 --> 00:02:18.360
Cloud discovers and uses them
and will later dive

00:02:18.420 --> 00:02:22.260
into building custom commands that
are primarily meant for execution

00:02:22.300 --> 00:02:23.680
by you instead.