Understand Example Skill and structure your own skills clearly

What the Example Skill Is

Example Skill is a reference skill from Anthropic's official claude-plugins-official repository, specifically from the example plugin contained within it. According to the provider, this skill demonstrates by example the structure and format used for Claude Code plugin skills, and it therefore serves less as a practical tool for a concrete task and more as a teaching example for developers who want to build their own new skills. According to its description, it activates when someone asks to demonstrate skills, show the skill format, create a skill template, or generally discusses skill development patterns.

The Basic Distinction Between Skills, Commands, and Agents

A central learning point of this reference example is the conceptual distinction it draws: skills are, according to the provider, model-invoked capabilities that Claude autonomously uses based on the task context. This sets them apart from commands, which are actively invoked by users, and from agents, which are spawned by Claude itself to handle a subtask. A skill therefore does not deliver standalone executable code but contextual guidance that Claude automatically incorporates into its responses whenever the skill's description matches the current user request.

Anatomy of a Skill

According to the guidance stored in the repository, a minimal skill consists of exactly one required file, a so-called SKILL.md, placed in the corresponding subfolder underneath the skill's name. Additional supporting files can optionally be added, such as an extra README file for more extensive documentation, a references directory for reference materials, an examples directory for sample files, and a scripts directory for helper scripts. According to the provider, this clear directory structure is meant to keep skills recognizable and consistently organized regardless of who develops them.

The Frontmatter Section and Its Role

At the top of every SKILL.md file sits, per the specification, a so-called frontmatter section carrying metadata. Mandatory within it are a unique name identifying the skill and a description defining the conditions under which Claude should draw on the skill. Optionally, a version number following semantic versioning and license information can also be recorded. According to the provider, the wording of the description is especially important: it should contain concrete trigger phrases that users might actually say, as well as topical keywords, so Claude reliably recognizes when the skill fits the matter at hand.

Practical Value for Skill Developers

The value of this reference example lies mainly in its usefulness as a direct template for building one's own skills, without having to piece together the formal requirements from scattered documentation. Anyone wanting to develop a skill for their own plugin can copy this example's structure and frontmatter and simply adjust the name, description, and content. This considerably lowers the barrier to entry, particularly because the skill includes additional best-practice guidance, such as the advice to focus each skill on a single, clearly bounded domain and to avoid overlap with the trigger conditions of other skills.

Limits of This Reference Example

It is important to note that the Example Skill itself does not solve any concrete subject-matter task; it serves purely as a structural template, so anyone looking for practical automation will not find direct functionality here. The skill also only describes the formal minimum requirements for a single plugin repository; how skills are organized, versioned, or protected against naming conflicts across larger collections of multiple plugins remains governed elsewhere in the more extensive official plugin-development documentation and should additionally be consulted before building a larger collection of one's own.