test1

Validate command-group sub-commands and SKILL.md metadata in CLI tools.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

test1 provides a minimal, self-contained unit to validate a command-group sub-command structure in a CLI tool, helping teams verify basic configuration quickly.

Core Features & Use Cases

  • Lightweight validation of mandatory metadata in SKILL.md (name and description).
  • Quick smoke testing of command-group sub-commands in small tooling projects.
  • Simple, language-agnostic instructions that can be executed by AI copilots to confirm setup.

Quick Start

Run test1 to validate the command-group sub-commands and ensure basic metadata loads.

Frequently Asked Questions about test1

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

FAQPage Schema
How do I validate command-group sub-commands in a CLI tool?▼

Lightweight CLI validation for command-group sub-commands helps teams verify basic configuration quickly. It acts as a self-contained test unit to confirm setup in small tooling projects without requiring complex test frameworks.

How do I run a quick smoke test on a small CLI toolchain?▼

To run a quick smoke test on a small CLI toolchain, execute the validation unit to confirm basic metadata loads and command-group sub-commands are structured correctly. The process provides simple, language-agnostic instructions for AI copilots.

Do I need specific dependencies to validate command-group sub-commands?▼

No dependencies are required for validating command-group sub-commands. The validation unit is self-contained and only requires a SKILL.md frontmatter with a name and description, optionally utilizing other directories if present.

What is the best way to verify mandatory metadata in SKILL.md for CLI validation?▼

The best way to verify mandatory metadata in SKILL.md is to run a lightweight validation unit that checks for required name and description fields. This confirms your command-group sub-commands have the necessary metadata loaded correctly.

Can I use this CLI validation approach for large toolchain projects?▼

This CLI validation approach is designed for small tooling projects and lightweight validation scenarios. It provides quick smoke testing for command-group sub-commands but may not be suitable for complex, large-scale toolchain validation needs.