good-skill

Validate Skill units by checking SKILL.md YAML frontmatter for required fields.

3|1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/HuXiangyu123/CUA-Lark-Agent --skill good-skill-huxiangyu123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: good-skill
Source: https://github.com/HuXiangyu123/CUA-Lark-Agent/tree/main/lark-cli/scripts/skill-format-check/tests/good-skill
Command: npx skills add https://github.com/HuXiangyu123/CUA-Lark-Agent --skill good-skill-huxiangyu123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that Skill units in a repository are properly defined by requiring a root SKILL.md with a valid YAML frontmatter containing at least a name and description, preventing misconfigurations during Skill discovery.

Core Features & Use Cases

  • Validates presence of SKILL.md at the Skill unit root.
  • Verifies YAML frontmatter fields: name, description, version (optional), and metadata as applicable.
  • Detects missing required fields and incorrect formatting to maintain a consistent Skill catalog.
  • Use Case: Run automated scans across a repo to surface invalid Skill units and generate a clean metadata catalog for onboarding.

Quick Start

Run the skill-format-check CLI against your project to validate all Skill units.

Frequently Asked Questions about good-skill

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

FAQPage Schema
How do I validate YAML frontmatter in SKILL.md files?

To validate YAML frontmatter in SKILL.md files, you need a tool that checks for the presence of required fields like name and description. This skill automates that verification to ensure metadata integrity across your repository.

What is the best way to find invalid Skill units in a repository?

Finding invalid Skill units involves scanning directories for a root SKILL.md and verifying its YAML frontmatter. Running automated scans surfaces missing required fields and incorrect formatting to maintain a consistent catalog.

How do I generate a metadata catalog for my Skill units?

Generating a metadata catalog requires extracting structured metadata blocks from valid Skill units. This skill catalogs optional components and dependencies, producing clean metadata including name, tagline, description, and keywords for onboarding.

Does Skill validation require specific fields in the YAML frontmatter?

Skill validation requires the YAML frontmatter to include at least a name and description. Version and metadata fields are optional, but missing required fields will flag the unit as invalid during the automated scan.

Why does my Skill unit fail formatting checks?

Skill units fail formatting checks when the root SKILL.md is missing or the YAML frontmatter lacks required name and description fields. Detecting missing required fields and incorrect formatting prevents misconfigurations during discovery.