template-skill

Define and validate self-contained Skill Units with SKILL.md and YAML frontmatter.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a ready-to-fill framework for defining new Claude skills quickly and consistently.

Core Features & Use Cases

  • Standardized Entry: A single SKILL.md frontmatter defines name, description, and deployment notes for discovery.
  • Self-Contained Unit: Optional scripts/references/assets directories support on-demand resources without altering the core skill.
  • Rapid Skill Prototyping: Duplicate and adapt the template to spin up new skills for different domains.

Quick Start

Use this template to create a new skill by replacing the placeholder values in SKILL.md and adding any optional resources as needed.

Frequently Asked Questions about template-skill

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

FAQPage Schema
How do I create reusable skill templates for rapid prototyping?

To create reusable skill templates, duplicate the framework and replace the placeholder values in SKILL.md. This provides a ready-to-fill structure for defining new skills quickly and consistently across different domains.

What is a SKILL.md frontmatter discovery contract?

A SKILL.md frontmatter discovery contract is YAML metadata that defines the name, description, and deployment notes for a skill. It acts as the standardized entry point for validating and activating a self-contained skill unit.

How do I add optional resources like scripts and references to a skill template?

Add optional resources by creating subdirectories named scripts/, references/, or assets/ within the skill unit. These directories load on demand to extend capability and provide richer context without altering the core skill.

Do I need dependencies to validate a self-contained skill unit?

No dependencies are required to validate a self-contained skill unit. The template only requires a SKILL.md file with a defined name and description to function as a valid, self-contained skill.

What's the best way to standardize skill metadata for discovery?

The best way to standardize skill metadata is using YAML frontmatter in a SKILL.md file. This defines the discovery contract by standardizing the entry with name, description, and deployment notes for consistent skill activation.