example-skill

Provides a reference template for creating Claude Code plugin skills.

1|Updated Jul 6, 2015
One-click install
npx skills add https://github.com/ksolomon/dotfiles --skill example-skill-ksolomon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: example-skill
Source: https://github.com/ksolomon/dotfiles/tree/main/AI/.claude/plugins/marketplaces/claude-plugins-official/plugins/example-plugin/skills/example-skill
Command: npx skills add https://github.com/ksolomon/dotfiles --skill example-skill-ksolomon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers building Claude Code plugins often lack a clear reference for how skills should be structured, what frontmatter fields are required, and how to write descriptions that trigger correctly. This Skill provides a canonical template and guidelines for authoring plugin skills. ## Core Features & Use Cases - Skill Structure Reference: Documents the required SKILL.md file and optional supporting directories such as references/, examples/, and scripts/. - Frontmatter Guidance: Explains required fields (name, description) and optional fields (version, license) with patterns for writing effective trigger descriptions. - Use Case: When scaffolding a new plugin skill, activate this Skill to get the correct directory layout, frontmatter format, and content best practices in one place. ## Quick Start Ask Claude to show the skill format or demonstrate how to create a skill template for a Claude Code plugin.

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 skill for a Claude Code plugin?▼

Create a directory under skills/ containing a SKILL.md file with YAML frontmatter defining a name and description, followed by Markdown instructions. Optionally add references/, examples/, or scripts/ subdirectories for supporting materials.

What frontmatter fields are required in a SKILL.md file?▼

The name and description fields are required. The description should specify trigger phrases and keywords so Claude knows when to invoke the skill. Version and license fields are optional.

How do I write a good skill description for triggering?▼

Include specific trigger phrases users might say, relevant keywords, and topic areas the skill covers. A good pattern lists quoted phrases and mentions the domain, so Claude activates the skill for the right queries.

What is the difference between skills, commands, and agents in Claude Code?▼

Skills are model-invoked capabilities Claude uses autonomously based on context. Commands are user-invoked, and agents are spawned by Claude. Skills provide contextual guidance incorporated into responses.

When should I add supporting directories to a skill?▼

Add references/ for in-depth documentation, examples/ for sample files, and scripts/ for helper scripts when the skill is complex. Keep simple skills to a single SKILL.md file to stay focused on one domain.