Sharing skills

The simplest way to share skills is by committing them to your repository under 'include/skills'. This ensures that anyone cloning the repository automatically gets these skills, providing a consistent experience for team coding standards and project-specific workflows. Updates are propagated on the next pull.

Sub-agents do not automatically inherit skills; they start with a fresh context. Built-in agents like explorer, plan, and verify cannot access skills at all. Only custom sub-agents can use skills when explicitly listed in an 'agent.mmd' file under 'include/agents'. These skills are loaded when the sub-agent starts, not on demand, so only relevant skills should be listed for specific expertise.

Skills can be shared through project directories for team access, plugins for cross-repository distribution, or enterprise deployment for organization-wide standards. For sub-agents, skills must be explicitly listed in their 'skills' field to ensure they are loaded at startup, and only skills relevant to the sub-agent's purpose should be included.

Skills can be distributed through plugins, which extend cloud code with custom functionality designed for sharing across teams and projects. Create a 'skills' directory within your plugin project, following a similar structure to the cloud directory. These plugins can then be distributed via a marketplace for community use, ideal for non-project-specific functionalities.

Administrators can deploy skills organization-wide through managed settings, prioritizing them over personal, project, and plugin skills with the same name. This method is crucial for enforcing mandatory standards, security requirements, compliance workflows, and consistent coding practices across the entire organization.