Question 1

How do I create a GitHub Copilot skill?

Accepted Answer

Create a folder containing a SKILL.md file with YAML frontmatter defining a name and description, followed by a Markdown body with the workflow. Add a resources directory with templates, examples, or checklists when they reduce ambiguity.

Question 2

What should go in a SKILL.md file?

Accepted Answer

A SKILL.md needs frontmatter with name and description, a when-to-use section with trigger phrases, an outcome standard, a concrete phased workflow, links to supporting resources, and a definition of done. Keep the body focused and move bulky content into resource files.

Question 3

How do I write a good skill description for discovery?

Accepted Answer

State both what the skill does and when to use it, including realistic user trigger phrases. Avoid descriptions that only name the topic, since agents rely on the description to decide when to activate the skill.

Question 4

When should I split content out of SKILL.md into resource files?

Accepted Answer

Move templates, examples, and detailed checklists into a resources folder when they bloat the main body. The SKILL.md should link to these files instead of duplicating them, keeping the workflow lean and readable.

Question 5

What are common mistakes when authoring Copilot skills?

Accepted Answer

Common failures include naming the skill after a topic instead of an activity, writing descriptions without trigger contexts, turning the body into theory instead of a procedure, and mixing multiple unrelated jobs into one skill.

creating-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

Frequently Asked Questions about creating-skills

Related Skills

Example Skill

a0-contribute-plugin

nested-agents-md-author

prompt-optimizer