make-skill-template

Scaffold new Copilot skills by duplicating a template into skills/<name>/ with SKILL.md.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/darkglow-net/github-copilot-kickstarter --skill make-skill-template-darkglow-net
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-skill-template
Source: https://github.com/darkglow-net/github-copilot-kickstarter/tree/main/.github/skills/make-skill-template
Command: npx skills add https://github.com/darkglow-net/github-copilot-kickstarter --skill make-skill-template-darkglow-net

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This meta-skill automates the creation of new Copilot skills by scaffolding a complete skill folder from a reusable template, ensuring consistent structure and frontmatter.

Core Features & Use Cases

  • Generate a ready-to-use Skill skeleton in skills/<name>/ with SKILL.md and optional directories (scripts/, references/, assets/).
  • Validate frontmatter (name and description) and enforce canonical folder-name alignment with downstream .github/skills copies.
  • Provide a quick-duplicate workflow to replicate the template for new skills and tailor the downstream copy for workspace needs.
  • Encourage standardized governance by updating root README.md Skills table when skills are added or renamed, keeping catalog synchronized.

Quick Start

Duplicate this folder to create a new skill, rename it to a lowercase hyphenated name, update SKILL.md with a matching frontmatter, and add any bundled resources.

Frequently Asked Questions about make-skill-template

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

FAQPage Schema
How do I scaffold a new Copilot skill from a template?

To scaffold a new Copilot skill, duplicate the make-skill-template structure into a new skills/<name>/ directory containing a SKILL.md file and optional resource folders like scripts, references, and assets.

What is the best way to standardize Copilot skill structure across multiple projects?

Standardize Copilot skill structure by using a reusable template that enforces frontmatter requirements like name and description, and maintains canonical folder-name alignment for consistent onboarding and prototyping across projects.

Does my Copilot skill SKILL.md require specific frontmatter?

Yes, your Copilot skill SKILL.md requires frontmatter validation. You must include the name and description fields in the frontmatter to ensure the skill skeleton meets canonical governance requirements.

How do I keep my workspace README synchronized when adding new Copilot skills?

Keep your workspace README synchronized by updating the root README.md Skills table whenever new skills are added or renamed, ensuring the catalog reflects the current skills directory structure.

Can I include optional directories like scripts and assets in my Copilot skill?

Yes, you can include optional directories such as scripts, references, and assets in your Copilot skill folder. The scaffolding process supports these directories alongside the required SKILL.md file.

What limitations exist when prototyping Copilot workflows with skill templates?

When prototyping Copilot workflows with skill templates, you are limited to the provided folder structure and frontmatter schema. Downstream governance requires manual README updates and folder-name alignment for workspace copies.