Make Skill Template
Scaffold a new GitHub Copilot Agent Skill folder with valid SKILL.md frontmatter and optional scripts, references, and assets.
Overview
Make Skill Template is an agent skill most often used in Build (also Validate, Operate) that scaffolds new GitHub Copilot Agent Skills with proper SKILL.md frontmatter and directory structure.
Install
npx skills add https://github.com/github/awesome-copilot --skill make-skill-templateWhat is this skill?
- Generates SKILL.md with required YAML frontmatter (name, keyword-rich description)
- Enforces lowercase hyphenated skill directories with optional scripts/references/assets
- Step-by-step scaffold aligned with Agent Skills specification
- Duplicable template starting point for specialized capabilities
- Trigger phrases: create a skill, make a new skill, scaffold a skill
- Required root file: SKILL.md with name and description frontmatter
- Optional bundled folders: scripts, references, assets, templates
Adoption & trust: 8.9k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know what capability you want Copilot to follow, but you lack a valid skill folder, triggers in the description, and optional bundled resources.
Who is it for?
Solo builders standardizing how they add Copilot skills after the first successful one-off workflow.
Skip if: Teams that only need a single inline prompt with no reusable SKILL.md or bundled resources.
When should I use this skill?
User asks to create a skill, make a new skill, scaffold a skill, or build specialized AI capabilities with bundled resources.
What do I get? / Deliverables
You get a lowercase hyphenated skills directory with a generated SKILL.md and optional scripts, references, and assets folders ready to implement and commit.
- skills/<skill-name>/ directory with SKILL.md
- Optional scripts/, references/, assets/ subfolders
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Creating specialized agent capabilities is core Build-phase work when extending what Copilot can do in the repo. Agent-tooling is the canonical shelf for skills that manufacture other skills and procedural bundles.
Where it fits
Scaffold a thin skill to test one automation before committing to a full workflow.
Generate SKILL.md and folders when adding a specialized integration skill to the repo.
Package procedural docs as a skill with references/ for consistent Copilot invocation.
Duplicate the template to split an overloaded skill into focused variants.
How it compares
Use instead of copying random markdown snippets that omit frontmatter triggers and spec-compliant layout.
Common Questions / FAQ
Who is make-skill-template for?
Solo and indie builders using GitHub Copilot who want to add durable Agent Skills with correct structure, not one-off chat instructions.
When should I use make-skill-template?
During Build when extending agent tooling, during Validate when scoping a prototype skill, or during Operate when refactoring skills—whenever you are asked to create, scaffold, or duplicate a skill.
Is make-skill-template safe to install?
Review the Security Audits panel on this Prism page before trusting the skill source; the skill itself is scaffolding guidance and does not mandate network or secret access by default.
SKILL.md
READMESKILL.md - Make Skill Template
# Make Skill Template A meta-skill for creating new Agent Skills. Use this skill when you need to scaffold a new skill folder, generate a SKILL.md file, or help users understand the Agent Skills specification. ## When to Use This Skill - User asks to "create a skill", "make a new skill", or "scaffold a skill" - User wants to add a specialized capability to their GitHub Copilot setup - User needs help structuring a skill with bundled resources - User wants to duplicate this template as a starting point ## Prerequisites - Understanding of what the skill should accomplish - A clear, keyword-rich description of capabilities and triggers - Knowledge of any bundled resources needed (scripts, references, assets, templates) ## Creating a New Skill ### Step 1: Create the Skill Directory Create a new folder with a lowercase, hyphenated name: ``` skills/<skill-name>/ └── SKILL.md # Required ``` ### Step 2: Generate SKILL.md with Frontmatter Every skill requires YAML frontmatter with `name` and `description`: ```yaml --- name: <skill-name> description: '<What it does>. Use when <specific triggers, scenarios, keywords users might say>.' --- ``` #### Frontmatter Field Requirements | Field | Required | Constraints | |-------|----------|-------------| | `name` | **Yes** | 1-64 chars, lowercase letters/numbers/hyphens only, must match folder name | | `description` | **Yes** | 1-1024 chars, must describe WHAT it does AND WHEN to use it | | `license` | No | License name or reference to bundled LICENSE.txt | | `compatibility` | No | 1-500 chars, environment requirements if needed | | `metadata` | No | Key-value pairs for additional properties | | `allowed-tools` | No | Space-delimited list of pre-approved tools (experimental) | #### Description Best Practices **CRITICAL**: The `description` is the PRIMARY mechanism for automatic skill discovery. Include: 1. **WHAT** the skill does (capabilities) 2. **WHEN** to use it (triggers, scenarios, file types) 3. **Keywords** users might mention in prompts **Good example:** ```yaml description: 'Toolkit for testing local web applications using Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or view browser console logs. Supports Chrome, Firefox, and WebKit.' ``` **Poor example:** ```yaml description: 'Web testing helpers' ``` ### Step 3: Write the Skill Body After the frontmatter, add markdown instructions. Recommended sections: | Section | Purpose | |---------|---------| | `# Title` | Brief overview | | `## When to Use This Skill` | Reinforces description triggers | | `## Prerequisites` | Required tools, dependencies | | `## Step-by-Step Workflows` | Numbered steps for tasks | | `## Troubleshooting` | Common issues and solutions | | `## References` | Links to bundled docs | ### Step 4: Add Optional Directories (If Needed) | Folder | Purpose | When to Use | |--------|---------|-------------| | `scripts/` | Executable code (Python, Bash, JS) | Automation that performs operations | | `references/` | Documentation agent reads | API references, schemas, guides | | `assets/` | Static files used AS-IS | Images, fonts, templates | | `templates/` | Starter code agent modifies | Scaffolds to extend | ## Example: Complete Skill Structure ``` my-awesome-skill/ ├── SKILL.md # Required instructions ├── LICENSE.txt # Optional license file ├── scripts/ │ └── helper.py # Executable automation ├── references/ │ ├── api-reference.md # Detailed docs │ └── examples.md