example-command

Demonstrate a SKILL.md frontmatter layout for slash-command skills.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/cjrfoto/claude-config --skill example-command-cjrfoto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: example-command
Source: https://github.com/cjrfoto/claude-config/tree/main/plugins/marketplaces/claude-plugins-official/plugins/example-plugin/skills/example-command
Command: npx skills add https://github.com/cjrfoto/claude-config --skill example-command-cjrfoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This example skill demonstrates how to structure a skill using the skills/<name>/SKILL.md frontmatter and layout for user-invoked commands.

Core Features & Use Cases

  • Demonstrates exact frontmatter fields (name, description, argument-hint, allowed-tools) and how they drive discovery and behavior.
  • Provides a minimal, testable slash-command style layout that can be reused as a template for new skills.
  • Serves as a reference example for documenting and validating skill metadata in the repository.

Quick Start

Invoke the example-command with a sample-arg to observe the frontmatter-driven layout.

Frequently Asked Questions about example-command

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

FAQPage Schema
How do I structure a slash-command skill using SKILL.md frontmatter?

SKILL.md frontmatter requires name and description fields to define a slash-command skill. Optional fields like argument-hint and allowed-tools can be added to specify command behavior and tool access within the claude-plugins-official repository.

What frontmatter fields are required for a Claude plugin skill layout?

A Claude plugin skill layout requires name and description fields in the frontmatter. Optional fields include argument-hint and allowed-tools, which help configure the slash-command style integration and validate skill metadata.

Can I use optional frontmatter fields to define allowed-tools in a skill?

Yes, you can define allowed-tools using optional frontmatter fields in the SKILL.md file. This example skill demonstrates how to structure these fields to specify tool access and argument-hint for user-invoked commands.

What is the best way to document skill metadata for slash-command style integration?

The best way to document skill metadata is by using the skills/<name>/SKILL.md layout. This template provides a minimal, testable structure that validates required and optional frontmatter fields for new commands.

Does the example-command skill layout support testing new frontmatter fields?

The example-command skill layout serves as a minimal, testable template for validating frontmatter fields. It ensures required fields are present and shows how optional fields like argument-hint drive command behavior.