Transcript of Sharing skills
Claude
0:02Skills become more valuable when shared.0:05A PR review skill that only you use is0:07helpful.0:08The same skill shared across your team0:10standardizes code review and provides a0:11consistent experience amongst your0:13organization, which much better.0:16Here are ways you can share your skills.0:20Now, the simplest sharing method is0:22committing skills to your repository.0:24Place them in .cloud/skills.0:27Anyone who clones a repository gets0:30these skills automatically. No extra0:32installation, it's just what you're0:33doing already.0:35When you push updates, everyone gets0:37them on the next pull. This works well0:39for team coding standards,0:41project-specific workflows, skills that0:43reference your code base structure.0:47Another way you can distribute your0:48skills is through plugins.0:51Think of plugins as ways to extend Cloud0:53Code with custom functionality, but0:55designed to be shared across teams and0:57projects.1:02In your plugin project, create a1:03directory called skills.1:05This will then follow a similar file1:06structure to the .cloud directory in our1:09project with the name of the skill with1:10a skill.md file.1:13And after you distribute your plugin to1:15a marketplace, other users can download1:17it into Cloud Code for themselves to1:19use.1:20This is best if your skills have1:22functionality that isn't too1:24project-specific and can be used by a1:26community members.1:30Administrators can deploy skills1:32organization-wide through managed1:33settings. Enterprise skills take highest1:36priority, like we discussed before, they1:38override personal project and plugin1:40skills with the same name.1:42This is for mandatory standards,1:44security requirements, compliance1:46workflows, coding practices that must be1:48consistent across the organization.1:51Keyword must.1:54Here's something that surprises people.1:56Sub agents don't automatically see your1:58skills.1:59Yeah.2:00When you delegate a task to a subagent,2:01it starts with a fresh clean context.2:04Built-in agents, like the explorer,2:06plan, and verify, can't access skills at2:09all. Only custom subagents you define2:11can use them, and only when you2:12explicitly list them. To create a custom2:15subagent with skills, add an agent.md2:17file in .claude/agents.2:20The skills field lists which skills to2:22load. These skills are loaded when the2:24subagent starts, not on demand like in2:26the main conversation. So, take that2:28into consideration.2:30First, ensure the skills exist.2:35Okay.2:36It exists.2:37Then, create the subagent using the2:39Claude code subagent creator.2:41If you have a subagent that you want to2:43add these skills to already, just go to2:44the existing agent.md file.2:47Then after that, create the skills field2:49and add your skills.2:51When you delegate to the subagent, it2:53has both skills loaded and applies them2:54to every single review.2:58Now, this pattern works really well when3:01you want isolated task delegation with3:03specific expertise.3:05Different subagents need different3:06skills. Front-end reviewer versus3:09back-end reviewer. You want to enforce3:11standards and delegate work without3:13relying on prompts. Only list skills3:15that are always relevant to the3:16subagent's purpose.3:21Share skills through project directories3:22for team access, plugins for3:24cross-repository distribution, or3:26enterprise deployment for3:28organization-wide standards. Subagents3:30don't inherit skills automatically. So,3:33list them explicitly in the subagent's3:34skills field. Built-in agents can't3:37access skills. Only custom subagents can3:39in your .claude/agents.3:42Skills load when the subagent starts, so3:44only list skills that are always3:46relevant to its purpose.
534 words · 105 lines
