example-skill

Demonstrate SKILL.md structure with YAML frontmatter and Markdown body.

4|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/dmgrok/mcp_mother_skills --skill example-skill-dmgrok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: example-skill
Source: https://github.com/dmgrok/mcp_mother_skills/tree/main/examples/skills/example-skill
Command: npx skills add https://github.com/dmgrok/mcp_mother_skills --skill example-skill-dmgrok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill demonstrates the proper SKILL.md structure and frontmatter needed for discovery and activation.

Core Features & Use Cases

  • Provides a validated example of a skill unit with a documented frontmatter and markdown body.
  • Serves as a learning template for building new skills and maintaining consistent documentation.
  • Use case: A developer or product team creates a new skill and uses this example to ensure proper formatting and guidance.

Quick Start

Load this example skill into your skill catalog to review the structure and understand the required fields.

Frequently Asked Questions about example-skill

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

FAQPage Schema
What is the required markdown structure for skill documentation and frontmatter?

To document a new skill properly, include YAML frontmatter with name and description fields, followed by a markdown body detailing operational instructions. This structure ensures proper skill discovery and activation.

How do I create a consistent markdown template for onboarding contributors to new skills?

To create a consistent markdown template for onboarding contributors, use a validated example demonstrating proper SKILL.md structure and frontmatter. This provides clear formatting guidance and maintains consistent documentation across new skills.

What should be included in YAML frontmatter for skill discovery and activation?

YAML frontmatter for skill discovery and activation must include the name and description fields. This metadata allows the skill to be properly identified and loaded into the skill catalog for operational use.

When do I need a standardized documentation template for my skill catalog?

You need a standardized documentation template for your skill catalog when a developer or product team creates new skills and requires a clear template to ensure proper formatting, usage documentation, and contributor onboarding.

Are there specific limitations when using a basic markdown template for skill documentation?

A limitation of using a basic markdown template for skill documentation is its focus on fundamental structure rather than complex internal design. It serves as a starting point and may require extension for advanced skill reasoning.