my-first-skill

Demonstrate SKILL.md creation with YAML frontmatter and progressive disclosure.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/gyChen-3725/myskills --skill my-first-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: my-first-skill
Source: https://github.com/gyChen-3725/myskills/tree/main/.claude/skills/my-first-skill
Command: npx skills add https://github.com/gyChen-3725/myskills --skill my-first-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provide a concise, concrete example that clarifies the required SKILL.md structure, frontmatter, and progressive disclosure so authors and testers avoid common formatting mistakes.

Core Features & Use Cases

  • Demonstrates mandatory YAML frontmatter with name and description and shows how to write the Markdown body in imperative form.
  • Shows resource resolution and where to place supplementary documentation in a references directory for deeper guidance.
  • Use cases include: onboarding new skill authors, validating OpenSkills loaders, and teaching best practices for skill packaging.

Quick Start

Load the my-first-skill SKILL.md to learn the SKILL.md format and test the OpenSkills loader.

Frequently Asked Questions about my-first-skill

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

FAQPage Schema
What is a SKILL.md file and when do I need to create one?

A SKILL.md file defines a packaged skill using mandatory YAML frontmatter for name and description alongside an imperative Markdown body. You need this format to author skills, validate OpenSkills loaders, or teach skill packaging best practices.

How do I structure YAML frontmatter and Markdown body for SKILL.md?

To structure a SKILL.md file, include mandatory YAML frontmatter containing name and description fields, followed by a Markdown body written in imperative form. This format clarifies progressive disclosure and prevents common formatting mistakes.

Where should I place supplementary documentation for a SKILL.md skill?

Place supplementary documentation in a references directory to demonstrate resource resolution. This directory structure provides deeper guidance and supports progressive disclosure for skill authors and testers using the OpenSkills loader.

Can I use a compact example directory to test OpenSkills loader behavior?

Yes, you can use a compact example directory to test OpenSkills loader behavior and validate SKILL.md parsing. This approach demonstrates resource resolution and frontmatter formatting without requiring complex skill packaging.

What are common formatting mistakes when writing SKILL.md files?

Common SKILL.md formatting mistakes include omitting mandatory YAML frontmatter fields like name and description, or writing the Markdown body outside the required imperative form. Following progressive disclosure best practices prevents these errors.

Do I need dependencies to validate SKILL.md structure?

No dependencies are required to validate SKILL.md structure. You only need a SKILL.md file with proper YAML frontmatter and an optional references directory to test loader resolution and demonstrate skill packaging.