demo-hello

Demonstrates SKILL.md YAML frontmatter and Markdown body for creating new skills.

Updated Mar 3, 2026

Search Tags:#templates #documentation #onboarding #yaml #structure #demo #skill

Ready to run

npx skills add https://github.com/DonYum/yf-skills --skill demo-hello

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: demo-hello
Source: https://github.com/DonYum/yf-skills/tree/main/skills/demo-hello
Command: npx skills add https://github.com/DonYum/yf-skills --skill demo-hello

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Demonstrate skill structure for new skills, helping teams understand how to build and document Skills consistently.

Core Features & Use Cases

Shows YAML frontmatter with name and description.
Includes a runnable Markdown body that explains usage and activation.
Serves as a reusable template for creating additional skills.

Quick Start

Copy this directory, adjust SKILL.md front matter and content, and test the Skill in your environment.

Frequently Asked Questions about demo-hello

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

FAQPage Schema

What is a skill structure template for developer onboarding?▼

A skill structure template provides a standardized directory and SKILL.md file with YAML frontmatter, enabling developers to consistently build, document, and validate new skills during onboarding.

How do I create a new skill using YAML frontmatter?▼

To create a new skill, copy the demo directory, adjust the SKILL.md YAML frontmatter with your name and description, add a runnable Markdown body, and test it in your environment.

Can I include optional directories when building skill documentation?▼

Yes, you can extend skill functionality by including optional directories such as scripts, references, and assets alongside the required SKILL.md file during the building process.

Does a basic skill template require dependencies to validate?▼

No dependencies are required to validate this basic skill template; it functions independently with just a SKILL.md file containing the proper YAML frontmatter and runnable Markdown content.

What is the best way to document skill usage for new developers?▼

The best way to document skill usage is using a reusable template containing YAML frontmatter and a runnable Markdown body that explains activation and usage, ensuring consistent team onboarding.

Why does my skill repository need a standardized structure?▼

Your skill repository needs a standardized structure to help teams understand how to build and validate skills consistently, reducing onboarding friction and ensuring documentation remains uniform.