Skills
A skill is a concise, repeatable methodology Claude follows in your conversation — a content-modeling playbook, an accessibility audit, a component scaffolder. Skills live inside plugin bundles and activate the moment they're relevant.
How skills work
Each skill is a single SKILL.md file with a clear scope, an allowed-tools list following least-privilege, and supporting reference material. When the right context appears — you mention an accessibility review, or scaffold a Sitecore component — Claude reaches for the skill and follows its instructions.
Skill vs. agent vs. resource
- Skill — a methodology Claude follows in your active conversation.
- Agent — a separate worker spawned for a contained, isolated task.
- Resource — static reference material (templates, prompt libraries, skeletons) Claude can read.
Finding the right skill
Skills are described by multiple optional facets, not a single hierarchy. On the browse page, narrow by what fits your context:
- Platform — vendor- or product-specific (Sitecore, Umbraco, Optimizely, Azure).
- Discipline — how a specific role does its work (engineering, design, strategy, security).
- Outcome — shaped by a deliverable (SEO, accessibility audit, performance).
- Lifecycle — the phase it applies to (plan, build, test-and-review, operate).
- Foundation only — cross-cutting primitives every workflow leans on (research, document templates).
Authoring a skill
See Authoring Standards for the rules every skill follows: structure, frontmatter, least-privilege tools, and the 500-line size limit. To contribute one, use the guided wizard — it hands you a pre-filled form, no git required.