make-skill-template

github/awesome-copilot · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/github/awesome-copilot --skill make-skill-template
0 commentsdiscussion
summary

Scaffold new Agent Skills with proper frontmatter, directory structure, and bundled resource organization.

  • Generates SKILL.md files with required YAML frontmatter (name, description) and optional metadata fields for skill discovery
  • Supports optional bundled directories: scripts/ for automation, references/ for documentation, assets/ for static files, and templates/ for starter code
  • Provides step-by-step workflow for creating skills from scratch or duplicating this template as a start
skill.md

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:

---
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:

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:

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             # Usage examples
├── assets/
│   └── diagram.png             # Static resources
└── templates/
    └── starter.ts              # Code scaffold

Quick Start: Duplicate This Template

  1. Copy the make-skill-template/ folder
  2. Rename to your skill name (lowercase, hyphens)
  3. Update SKILL.md:
    • Change name: to match folder name
    • Write a keyword-rich description:
    • Replace body content with your instructions
  4. Add bundled resources as needed
  5. Validate with npm run skill:validate

Validation Checklist

  • Folder name is lowercase with hyphens
  • name field matches folder name exactly
  • description is 10-1024 characters
  • description explains WHAT and WHEN
  • description is wrapped in single quotes
  • Body content is under 500 lines
  • Bundled assets are under 5MB each

Troubleshooting

Issue Solution
Skill not discovered Improve description with more keywords and triggers
Validation fails on name Ensure lowercase, no consecutive hyphens, matches folder
Description too short Add capabilities, triggers, and keywords
Assets not found Use relative paths from skill root

References

how to use make-skill-template

How to use make-skill-template on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add make-skill-template
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/github/awesome-copilot --skill make-skill-template

The skills CLI fetches make-skill-template from GitHub repository github/awesome-copilot and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/make-skill-template

Reload or restart Cursor to activate make-skill-template. Access the skill through slash commands (e.g., /make-skill-template) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.739 reviews
  • Lucas Ramirez· Dec 20, 2024

    Keeps context tight: make-skill-template is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Hassan Haddad· Dec 12, 2024

    make-skill-template is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Rahul Santra· Nov 27, 2024

    We added make-skill-template from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Layla Sharma· Nov 11, 2024

    Registry listing for make-skill-template matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Aanya Srinivasan· Nov 7, 2024

    make-skill-template fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Evelyn Wang· Nov 3, 2024

    make-skill-template reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Emma Zhang· Oct 26, 2024

    We added make-skill-template from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Anaya Thomas· Oct 22, 2024

    Registry listing for make-skill-template matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Pratham Ware· Oct 18, 2024

    make-skill-template fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Layla Kapoor· Oct 2, 2024

    make-skill-template reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 39

1 / 4