template

Create new Skill Units with standardized YAML frontmatter and Markdown body.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ZiadNagar/zeVillage-AI-Toolkit --skill template-ziadnagar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template
Source: https://github.com/ZiadNagar/zeVillage-AI-Toolkit/tree/main/template
Command: npx skills add https://github.com/ZiadNagar/zeVillage-AI-Toolkit --skill template-ziadnagar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This template Skill Unit provides a ready-to-fill scaffold for creating new skills, ensuring consistent frontmatter and structure across the repository.

Core Features & Use Cases

  • Standard YAML frontmatter with required fields (name and description) and a descriptive body for operational instructions.
  • Optional directories (scripts/, references/, assets/) can be added to extend the Skill Unit as needed.
  • Smooth onboarding for contributors by providing a repeatable, validated starting point.

Quick Start

Copy this template into a new skill directory and replace the frontmatter name/description and body with your own skill instructions.

Frequently Asked Questions about template

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

FAQPage Schema
How do I create a new skill unit with standardized YAML frontmatter?

To create a new skill unit with standardized YAML frontmatter, copy a clean template scaffold into a new directory and replace the required name and description fields with your specific metadata.

What is the required metadata structure for a skill unit scaffold?

The required metadata structure for a skill unit scaffold is a YAML frontmatter block containing at least the name and description fields, followed by a Markdown body for operational instructions.

Can I add optional directories like scripts and assets to my skill unit?

Yes, you can extend your skill unit by adding optional component directories such as scripts, references, and assets to support the Markdown operational instructions and YAML metadata.

How do I enforce consistent documentation conventions across a skills repository?

You enforce consistent documentation conventions across a skills repository by applying a standardized template that validates the YAML frontmatter structure and Markdown body for every newly added skill unit.

What is the best way to onboard contributors to write skill metadata?

The best way to onboard contributors is providing a repeatable, ready-to-fill template with pre-defined YAML frontmatter conventions, reducing formatting errors and ensuring validated metadata structure.