github-copilot-agent-skills

Create, review, and package portable GitHub Copilot Agent Skills with SKILL.md contracts.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/schattenspiegel/skill-foundry-skills --skill github-copilot-agent-skills-schattenspiegel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-copilot-agent-skills
Source: https://github.com/schattenspiegel/skill-foundry-skills/tree/main/skills/github-copilot-agent-skills
Command: npx skills add https://github.com/schattenspiegel/skill-foundry-skills --skill github-copilot-agent-skills-schattenspiegel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building a reusable GitHub Copilot Agent Skill requires precise metadata, discovery triggers, and verification steps that are easy to get wrong, leading to skills that fail to activate or leak authoring artifacts. ## Core Features & Use Cases - Skill Authoring Workflow: Guides you through defining one repeated job, triggers, boundaries, and completion evidence before writing SKILL.md frontmatter. - Contract and Pattern References: Bundled references define the SKILL.md artifact contract, reusable skill patterns, and verification procedures. - Use Case: You want Copilot to automatically review API contract changes in your repository. Use this Skill to scaffold a lowercase kebab-case skill directory, write a precise description with non-goals, link reference resources, and verify explicit and implicit discovery in VS Code. ## Quick Start Ask the agent to create a new Copilot skill for a repeated task, including its triggers, resources, and verification steps.

Frequently Asked Questions about github-copilot-agent-skills

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

FAQPage Schema
How do I create a GitHub Copilot Agent Skill?▼

Create a lowercase kebab-case directory containing a SKILL.md file with YAML frontmatter defining name and description. Place it in .github/skills for project scope or ~/.copilot/skills for personal scope, then write the workflow instructions in the Markdown body.

What fields are required in SKILL.md frontmatter?▼

Only name and description are required. The name must be lowercase kebab-case matching the directory, and the description should front-load the job and non-goals. Optional fields like argument-hint and user-invocable depend on host support.

Where does VS Code discover Copilot skills?▼

VS Code discovers skills in project locations such as .github/skills and .agents/skills, and user locations like ~/.copilot/skills. Host settings can add locations, so verify the installed version before relying on a path.

When should I not use an Agent Skill?▼

Avoid skills for always-on repository rules, single prompt commands, custom agent personas, or tasks fully expressible in one short prompt. Skills suit repeated multi-step jobs that benefit from automatic discovery and reusable references.

How do I test that a Copilot skill triggers correctly?▼

Test explicit slash invocation, implicit discovery, baseline improvement, and negative non-trigger cases separately. Also inspect VS Code slash discovery and confirm linked resources resolve one hop from SKILL.md.