test3

Validate Skill units by checking YAML frontmatter in SKILL.md files.

1|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/fdshg693/ZENN --skill test3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test3
Source: https://github.com/fdshg693/ZENN/tree/main/skills/command-group/sub_commands/test/test3
Command: npx skills add https://github.com/fdshg693/ZENN --skill test3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill unit provides a minimal, self-describing template to support automatic discovery and validation of Skill units by requiring a SKILL.md with a name and description at the root.

Core Features & Use Cases

  • Lightweight metadata validation: ensures SKILL.md exists and contains name and description.
  • Discovery readiness: helps tooling enumerate valid skills for indexing and activation.
  • Minimal footprint: no external scripts required for basic validation.

Quick Start

Place a new skill directory with a valid SKILL.md frontmatter and run the Skill loader to activate this skill.

Frequently Asked Questions about test3

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

FAQPage Schema
How do I validate YAML frontmatter metadata for a skill repository?▼

To validate YAML frontmatter metadata, ensure the root of your skill directory contains a SKILL.md file with required name and description fields, then run the loader to parse and verify its discovery readiness.

What is a discovery-ready skill unit and how does metadata validation work?▼

A discovery-ready skill unit is a directory containing a SKILL.md with valid YAML frontmatter, which validation parses to extract name and description, assess components, compute dependencies, and perform toxicity safety checks.

How do I make my command-subcommand skill unit discoverable for indexing?▼

Make your skill unit discoverable by placing a SKILL.md file with name and description frontmatter at the root, optionally including scripts, references, or assets directories for validation and indexing.

Does skill metadata validation require external scripts or dependencies?▼

Basic metadata validation requires no external scripts or dependencies, relying solely on a minimal SKILL.md footprint to parse frontmatter, assess components, compute dependencies, and check for safety risks.

What limitations exist when validating skill units with frontmatter?▼

Validation is limited to directories under skills containing a SKILL.md, focusing on frontmatter parsing and toxicity checks, and does not execute external scripts or validate logic beyond metadata discovery readiness.

Why does my skill unit fail validation during discovery?▼

Skill unit validation fails during discovery if the root directory lacks a SKILL.md file or if the YAML frontmatter is missing required name and description fields needed to generate a metadata payload.