ck:template-skill

Generate standardized Skill Unit metadata from SKILL.md frontmatter.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/haidonglethqb/CloudSchool --skill ck-template-skill-haidonglethqb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:template-skill
Source: https://github.com/haidonglethqb/CloudSchool/tree/main/.qwen/skills/template-skill
Command: npx skills add https://github.com/haidonglethqb/CloudSchool --skill ck-template-skill-haidonglethqb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill Unit template provides a ready-to-use scaffold for creating new skills by standardizing metadata extraction from a SKILL.md frontmatter and ensuring consistent discovery attributes.

Core Features & Use Cases

  • Standardization: Enforces a consistent frontmatter schema (name, description) and a consistent description structure for discovery.
  • Scaffold Creation: Generates or validates metadata for new Skill Units, ensuring dependencies and components are correctly declared.
  • Use Case: A development team wants to rapidly onboard new skills with uniform metadata and clear activation instructions.

Quick Start

Place a valid SKILL.md at the root of a directory to mark it as a Skill Unit and fill in the mandatory name and description in YAML frontmatter, then add optional resources as needed.

Frequently Asked Questions about ck:template-skill

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

FAQPage Schema
How do I generate YAML skeleton metadata for a new Skill Unit?

To generate YAML skeleton metadata for a new Skill Unit, provide a SKILL.md frontmatter to extract standardized values for name, tagline, description, dependencies, and components, outputting a single formatted YAML document.

What is the standard frontmatter schema required for Skill Unit discovery?

The standard frontmatter schema for Skill Unit discovery requires mandatory name and description fields in YAML format, ensuring consistent discovery attributes and uniform metadata structure across new skills.

How do I validate optional directories and fields when creating skill metadata?

To validate optional directories and fields when creating skill metadata, process the SKILL.md frontmatter to verify required fields are present and optional directories exist before outputting a strictly formatted YAML document.

What is the best way to standardize skill metadata for team onboarding?

The best way to standardize skill metadata for team onboarding is using a template that enforces a consistent YAML frontmatter schema, ensuring dependencies and components are correctly declared for rapid and uniform skill activation.

Do I need any dependencies to use the Skill Unit template?

No, the Skill Unit template requires no external dependencies, allowing you to directly generate and validate metadata from a SKILL.md file placed at the root directory of your project.