Transcript of Creating your first skill
Claude
0:03So, let's create a skill. This skill0:06will teach Claude how we would like it0:08to explain code using visual diagrams0:10and analogies. [music]0:11Then, we'll look at what happens under0:14the hood when Claude uses it.0:18First, [music] let's create a directory0:20for your skill. We're going to be making0:22a personal skill, so it'll live in many0:24projects, so it will go in your home0:26directory. Take into consideration that0:28we're creating a directory with the0:29skill name inside of the skills0:31directory.0:33Now create the skill.0:38The name identifies your skill. The0:41description tells Claude when to use it.0:43This is the matching criteria. And then0:46everything after the second dashes is0:49the instructions that Claude follows.0:52Cloud code loads skills at startup. So0:55restart your session. Then verify it's0:57available.1:00You should see PR description in the1:02list.1:04Now test it. Make some changes on a1:07branch and say, "Write a PR description1:09for my changes."1:11Claude will then show you that it's1:13using the PR description skill.1:17After that, it'll check your diff and1:18write a description following your1:20template. Same format every single time.1:24When Cloud Code starts, it scans four1:26locations for skills. Enterprise paths,1:29your personal Claude skills, the1:31project's Claude skills, and installed1:33plugins. It loads only the name and1:35description of each skill, not the full1:37content. This is important later. When1:40you send a request, Claude compares it1:41to the descriptions of your skills.1:43Explain what this function does matches1:45a skill described as explain code with1:47visual diagrams because the intent1:49overlaps. It will then ask you to1:51confirm loading up the skill. This1:53confirmation step keeps you aware of1:55what context Claude is using. After you1:58confirm, Claude reads the complete file2:00and follows its instructions. Now, let's2:02say you clone a Git repository and have2:04an overlapping skill name. Well, which2:07one wins? Here's the priority list. The2:11highest is enterprise, which lives in2:13the manage settings. Two is the2:15personal, which lives in your root2:17directory configuration like we're doing2:19right now. Three is the project which is2:21the claw directory inside of your2:23repository. And the lowest is the2:25plugins where you store your plugins2:27that you got online. This lets2:29organizations enforce standards while2:31allowing individual customization2:33through differently named skills. If2:35your company has an enterprise code2:38review skill and you create a personal2:40code review skill, the enterprise2:42version of that takes precedence. To2:44avoid conflicts, use descriptive names.2:47Instead of review, use front-end PR2:50review or security review. To update a2:53skill, edit it skill.md file. Simple. To2:57remove one, delete its directory.3:00Restart clock code after changes for3:02them to take effect.3:06Creating a skill means making a3:08directory with a skill.md file3:10containing metadata and instructions.3:13Claude loads skill names and3:15descriptions at startup. matches3:17incoming requests against those3:19descriptions and asks for confirmation3:22before loading the full content.3:25Priority rules handling name conflicts.3:27Enterprise overrides personal personal3:29overrides project overrides plugins.3:32[music] Edit the skill.md file to update3:34a skill and restart cloud code for3:36changes to take effect.
522 words · 91 lines
