template-skill

Create standardized Skill scaffolds with SKILL.md frontmatter and Markdown instructions.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/guihousun/NTL-GPT-Clone --skill template-skill-guihousun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-skill
Source: https://github.com/guihousun/NTL-GPT-Clone/tree/main/skills/template-skill
Command: npx skills add https://github.com/guihousun/NTL-GPT-Clone --skill template-skill-guihousun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a ready-to-use skeleton with a YAML frontmatter and a Markdown body, helping teams standardize new Skill units.

Core Features & Use Cases

  • Standardized frontmatter for name, description, tagline, category, keywords, and dependencies.
  • Optional resource directories (scripts/, references/, assets/) to extend functionality as needed.
  • Clear Quick Start guidance to reproduce or customize the Skill structure.

Quick Start

Duplicate this template directory, rename it, and replace the frontmatter name and description with your new skill details.

Frequently Asked Questions about template-skill

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

FAQPage Schema
How do I structure a new skill using markdown and frontmatter?

To structure a new skill, use a standardized SKILL.md file combining YAML frontmatter for metadata and a Markdown body for operational instructions. This enforces required fields like name, description, category, keywords, and dependencies for consistent scaffolding.

What metadata is required in skill frontmatter?

Required skill frontmatter metadata includes name, description, tagline, category, keywords, dependencies, components, and toxicity flags. JSON and YAML formatting rules are strictly enforced to validate this structural metadata for operational units.

How do I create a standardized skill scaffold for dev workflows?

Duplicate the template directory, rename it, and replace the frontmatter name and description with your new skill details. This provides a ready-to-use skeleton with optional scripts, references, and assets directories for extending functionality.

Can I include optional resources like scripts and references in my skill structure?

Yes, you can extend skill functionality by adding optional resource directories such as scripts/, references/, and assets/ alongside the main SKILL.md file for on-demand usage during operational tasks and workflows.

What is the best way to standardize new skill units for development teams?

The best way to standardize new skill units is applying a consistent SKILL.md scaffold with predefined YAML frontmatter and Markdown body, ensuring all developers follow identical metadata requirements and formatting rules across projects.