example-skill

Create standardized Claude Code plugin skills with SKILL.md frontmatter and optional directories.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/onelee85/my-skills --skill example-skill-onelee85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: example-skill
Source: https://github.com/onelee85/my-skills/tree/main/claude-plugins-official/plugins/example-plugin/skills/example-skill
Command: npx skills add https://github.com/onelee85/my-skills --skill example-skill-onelee85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This template provides a ready-to-use, consistent structure to create Claude Code plugin skills, enabling teams to quickly define the entry point and usage guidelines.

Core Features & Use Cases

  • Standard SKILL.md with required frontmatter (name and description) and a clear description of activation conditions.
  • Optional supporting directories such as references/, assets/, and scripts/ to organize guidance and resources for more complex skills.

Quick Start

Copy the example-skill skeleton into your project and tailor the frontmatter and body to your domain.

Frequently Asked Questions about example-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude Code plugin skill with the correct frontmatter structure?

To create a Claude Code plugin skill, you use a standardized template ensuring each skill includes a SKILL.md file with required YAML frontmatter containing name and description fields, plus an optional descriptive Markdown body.

What is the required structure for a SKILL.md file in skill development?

A SKILL.md file requires YAML frontmatter with at least name and description fields, followed by a descriptive Markdown body explaining activation conditions and usage guidelines for the skill.

Can I include scripts and references when building a Claude Code plugin skill?

Yes, you can organize complex skills by adding optional subdirectories for scripts, references, and assets alongside the SKILL.md file to store guidance and resources.

What is the best way to standardize skill templates for a team working with Claude Code?

The best way to standardize skill templates is copying a reference skeleton into your project and tailoring the YAML frontmatter and Markdown body to your specific domain requirements.

Do I need optional directories like assets and references for every skill template?

No, you do not need optional directories for every skill template; the subdirectories for scripts, references, and assets are optional and only used for organizing more complex skills.

Why does my Claude Code plugin skill need a description in the frontmatter?

Your skill needs a description in the frontmatter to define activation conditions and provide a clear entry point for usage, ensuring the plugin knows when and how to apply the skill.