Video: Sharing skills
1. Video: Sharing skills
Skills become more valuable when shared. A PR review skill that only you use is helpful. The same skill shared across your team standardizes code review and provides a consistent experience amongst your organization which much better. Here are ways you can share your skills. Now the simplest sharing method is committing skills to your repository. Place them include/skills. Anyone who clones a repository gets these skills automatically. No extra installation. It's just what you're doing already. When you push update, everyone gets them on the next poll. This works well for team coding standards, project specific workflows, skills that reference your codebase structure. Another way you can distribute your skills is through plugins. Think of plugins as ways to extend Claude Code with custom functionality, but designed to be shared across teams and projects. In your plug-in project, create a directory called skills. This will then follow a similar file structure to the cloud directory in our project with the name of the skill with a skill.md file. And after you distribute your plugin to a marketplace, other users can download it into cloud codes for themselves to use. This is best if your skills have functionality that isn't too project specific and can be used by community members. Administrators can deploy skills organizationwide through managed settings. Enterprise skills take highest priority. Like we discussed before, they override personal project and plug-in skills with the same name. This is for mandatory standards, security requirements, compliance workflows, coding practices that must be consistent across the organization. Keyword must. Here's something that surprises people. Sub agents don't automatically see your skills. Yeah, when you delegate a task to a subagent, it starts with a fresh, clean context. Built-in agents like the explorer, plan, and verify can't access skills at all. Only custom sub agents you define can use them and only when you explicitly list them. To create a custom subagent with skills, add an agent.mmd file include/ aents. The skills field lists which skills to load. These skills are loaded when the subagents starts, not in demand like in the main conversation. So take that into consideration. First ensure the skills exist. Okay, it exists. Then create the subagent using the Claude Code subagents creator. If you have a subagent that you want to add these skills to already just go to the existing agent.md file. Then after that create the skills fields and add your skills. When you delegate to the subagent it has both skills loaded and applies them to every single review. Now this pattern works really well when you want isolated task delegation with specific expertise. Different sub agents need different skills. Front-end reviewer versus back-end reviewer. You want to enforce standards and delegated work without relying on prompts. Only list skills that are always relevant to the subage's purpose. Share skills through project directories for team access, plugins for cross repository distribution, or enterprise deployment for organizationwide standards. Sub agents don't inherit skills automatically, so list them explicitly in the sub agents skills field. Built-in agents can't access skills. Only custom sub agents can in your Claude/ agents. Skills load when the sub agents start, so only list skills that are always relevant to its purpose.2. Let's practice!
Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.