example-command

Define a minimal skill with frontmatter metadata and a simple activation body.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This example skill provides a clear template for building user-invoked commands, showing how to define frontmatter, layout, and a basic activation flow.

Core Features & Use Cases

  • Frontmatter-based metadata for name, description, and options
  • Simple instruction flow for parsing user input and performing a task
  • Demonstrates the skills/<name>/SKILL.md layout and backward compatibility with legacy command formats

Quick Start

Invoke the example-command with a sample argument to observe the parsing and response.

Frequently Asked Questions about example-command

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

FAQPage Schema
How do I define a skill using frontmatter and a simple activation body?

Defining a skill requires a frontmatter header declaring name, description, and options, followed by a simple activation body. The skills/<name>/SKILL.md layout processes this metadata to enable user invocation and command parsing.

What is the SKILL.md layout used for in command invocation?

The SKILL.md layout establishes the directory structure for skill discovery and user invocation. It uses frontmatter to define command metadata and an activation body to parse input, satisfying requirements for testing.

How do I declare command options in skill frontmatter?

Command options are declared in the frontmatter header alongside name and description. This metadata structure defines how arguments are parsed during invocation, providing a clear template for building user-invoked commands.

Does the skill layout support backward compatibility with legacy command formats?

Yes, the skill layout supports backward compatibility with legacy command formats. The skills/<name>/SKILL.md structure maintains this compatibility while using frontmatter-based metadata for defining name, description, and options.

What's the best way to learn how command parsing works in a skill?

Invoking an example command with a sample argument demonstrates how command parsing works. Observing the response shows how frontmatter metadata maps to the activation body, illustrating the flow from user input to task execution.

When do I need frontmatter metadata for a user-invoked command?

Frontmatter metadata is needed whenever creating a user-invoked command for discovery and testing. It defines the name, description, and options required by the skills/<name>/SKILL.md layout to properly route and parse user input.