Automated summary
Guides the creation of GitHub Copilot customizations—custom agents, prompts, instructions, and collections—using templates and conventions from the awesome-copilot community toolkit.
Strengths
- Provides concrete file templates for Copilot agents, prompts, and instructions.
- Explains naming conventions, file structure, and expected extensions.
- Includes a quick-reference table mapping each component type to its purpose and access method.
- Draws on a large community catalog with 200+ agents, 180+ prompts, and 150+ instructions.
Limitations
- Focuses on GitHub Copilot's customization format, which may change over time.
- Templates are skeletal and leave domain expertise and validation of generated files to the user.
- Does not deeply cover testing, debugging, or governance of generated customizations.
Use when you need to scaffold or standardize GitHub Copilot agents, prompts, instructions, or collections for a project or team.
Avoid when you need general prompt engineering or AI-agent design guidance outside the GitHub Copilot customization ecosystem.
Security analysis
SafeThis skill is purely instructional documentation for authoring GitHub Copilot customization files (agents, prompts, instructions, collections). It declares no tools, and the only executable snippets are conventional project maintenance commands (npm run validate/build, a line-endings fix script) referenced as part of a described repository workflow rather than instructions to run anything destructive. No network exfiltration, obfuscation, credential handling, or safety-disabling content is present.
No concerns found
How this analysis is madeExamples
Create a custom GitHub Copilot agent named database-migration-specialist.agent.md that reviews PostgreSQL migration scripts for safety and rollback coverage. Include frontmatter with description, model, and any MCP tools it needs.Write a GitHub Copilot instructions file for React/TypeScript projects that applies to **/*.tsx, enforces functional components and hooks, and includes DO and DON'T examples.Create a reusable GitHub Copilot prompt file called create-readme.prompt.md that generates a project README from package.json and the source tree, with clear requirements and an output format.name: awesome-copilot description: Expert guidance for creating GitHub Copilot customizations including custom agents, prompts, instructions, and collections. Based on the awesome-copilot community toolkit with 200+ agents, 180+ prompts, and 150+ instructions. Use when customizing GitHub Copilot, creating specialized AI agents, writing coding standards, or building developer productivity tools.
Awesome GitHub Copilot Customization Expert
Expert guidance for creating and managing GitHub Copilot customizations based on the community-curated awesome-copilot toolkit. Create custom agents, prompts, instructions, and collections to enhance developer productivity.
Core Capabilities
- Custom Agents - Create specialized AI personas with specific expertise
- Prompts - Build reusable task templates for common workflows
- Instructions - Define coding standards that auto-apply based on file patterns
- Collections - Organize customizations into themed groupings
- Best Practices - Community-curated standards and patterns
Quick Reference
Component Types
| Type | Purpose | File Extension | Access Method |
|------|---------|---------------|---------------|
| Agents | Specialized AI personas | .agent.md | Select in Copilot Chat or CCA |
| Prompts | Task-specific templates | .prompt.md | /awesome-copilot <command> |
| Instructions | Auto-applying standards | .instructions.md | Automatic by file pattern |
| Collections | Curated groupings | .collection.md | Browse in Copilot extensions |
Instructions
Creating Custom Agents
File Structure:
agents/
├── my-expert.agent.md
├── database-specialist.agent.md
└── security-reviewer.agent.md
Agent File Template:
---
description: 'Clear description of what this agent does'
model: claude-3-5-sonnet-20241022
tools:
- mcp-server-name # Optional: MCP servers this agent uses
---
# Agent Name
## Role
You are a [specific role] specializing in [domain].
## Expertise
- Skill area 1
- Skill area 2
- Skill area 3
## Guidelines
1. Always follow [specific pattern]
2. Consider [important aspects]
3. Provide [expected outputs]
## Examples
[Concrete examples of expected interactions]
Naming Conventions:
- Lowercase only:
python-expert.agent.md - Hyphens for spaces:
database-migration-specialist.agent.md - Descriptive and clear:
azure-bicep-architect.agent.md
Creating Prompts
File Structure:
prompts/
├── create-readme.prompt.md
├── optimize-sql.prompt.md
└── generate-tests.prompt.md
Prompt File Template:
---
title: Descriptive Prompt Title
description: What this prompt does and when to use it
---
# System Instructions
You are tasked with [specific task].
## Context
[Background information needed]
## Requirements
1. Must include [requirement 1]
2. Should follow [requirement 2]
3. Output format: [expected format]
## Process
1. Step 1
2. Step 2
3. Step 3
## Example Output
```[language]
[Example of expected output]
**Usage:**
In GitHub Copilot Chat:
/awesome-copilot create-readme /awesome-copilot optimize-sql
---
### Creating Instructions
**File Structure:**
instructions/ ├── csharp.instructions.md ├── react.instructions.md └── terraform.instructions.md
**Instruction File Template:**
```markdown
---
description: Coding standards for [technology/framework]
patterns:
- '**/*.cs' # File patterns to apply to
- '**/src/**/*.tsx'
---
# [Technology] Best Practices
## Code Style
- Follow [specific style guide]
- Use [naming conventions]
- Organize files as [structure]
## Patterns
**DO:**
```[language]
// Good example
DON'T:
// Bad example
Common Scenarios
Scenario 1: [Common Task]
[Specific guidance]
Scenario 2: [Another Task]
[More guidance]
References
- [Documentation link]
- [Style guide link]
**Auto-Application:**
Instructions automatically apply when editing files matching the patterns.
---
### Creating Collections
**File Structure:**
collections/ ├── devops-toolkit.collection.md ├── security-essentials.collection.md └── azure-specialists.collection.md
**Collection File Template:**
```markdown
---
title: Collection Name
description: What this collection provides
---
# Collection Name
Curated collection of [theme] customizations.
## Included Items
### Agents
- [agent-name](../agents/agent-name.agent.md) - Description
- [another-agent](../agents/another-agent.agent.md) - Description
### Prompts
- [prompt-name](../prompts/prompt-name.prompt.md) - Description
- [another-prompt](../prompts/another-prompt.prompt.md) - Description
### Instructions
- [instruction-name](../instructions/instruction-name.instructions.md) - Description
## Use Cases
1. Use case 1
2. Use case 2
3. Use case 3
## Getting Started
[Quick start guide for this collection]
Common Patterns
Language-Specific Agent
---
description: 'Expert in [Language] with focus on modern practices and performance'
model: claude-3-5-sonnet-20241022
---
# [Language] Expert
## Expertise
- Modern [Language] features
- Performance optimization
- Testing frameworks
- Popular libraries and frameworks
## Coding Standards
- Use [style guide]
- Follow [naming conventions]
- Prefer [patterns]
## Common Tasks
- Code review with security focus
- Performance optimization
- Refactoring legacy code
- Writing comprehensive tests
DevOps Workflow Prompt
---
title: Generate CI/CD Pipeline
description: Creates GitHub Actions or Azure Pipelines workflow
---
# CI/CD Pipeline Generator
Generate a complete CI/CD pipeline with:
## Requirements
1. Build stage with dependency caching
2. Test stage with coverage reporting
3. Security scanning
4. Deployment stages (dev, staging, prod)
5. Approval gates for production
## Platform-Specific
- **GitHub Actions**: Use reusable workflows
- **Azure Pipelines**: Use YAML templates
- **Jenkins**: Use declarative pipeline
## Best Practices
- Fail fast on critical errors
- Parallel execution where possible
- Secrets management via key vault
- Artifact storage and versioning
Framework Instruction Set
---
description: Best practices for [Framework] development
patterns:
- '**/*.jsx'
- '**/*.tsx'
- '**/components/**'
---
# [Framework] Development Standards
## Component Structure
components/ ├── ComponentName/ │ ├── index.ts # Barrel export │ ├── ComponentName.tsx │ ├── ComponentName.test.tsx │ ├── ComponentName.styles.ts │ └── types.ts
## Coding Rules
1. Use functional components with hooks
2. Extract business logic into custom hooks
3. Implement proper TypeScript types
4. Write unit tests for all components
5. Use CSS-in-JS or CSS modules
## Anti-Patterns
- Avoid prop drilling (use context)
- Don't mutate state directly
- Keep components single-responsibility
Best Practices
Agent Design
- Single Responsibility - Each agent should have one clear expertise
- Specific Context - Provide concrete guidelines, not generic advice
- Include Examples - Show expected interactions and outputs
- Reference Standards - Link to official docs and style guides
- Test Thoroughly - Validate agent responses before deployment
Prompt Engineering
- Clear Instructions - Be explicit about requirements
- Structured Output - Define expected format precisely
- Error Handling - Include guidance for edge cases
- Context Limits - Keep prompts focused and concise
- Reusable - Design for multiple similar use cases
Instruction Quality
- Pattern Matching - Use specific glob patterns for file targeting
- Comprehensive Coverage - Address common scenarios thoroughly
- Prioritize DO's - Show correct patterns prominently
- Explain Why - Include rationale for standards
- Keep Updated - Review as frameworks evolve
Collection Curation
- Themed Grouping - Organize by workflow or domain
- Complete Coverage - Include all needed components
- Cross-Reference - Link related items clearly
- Onboarding Guide - Help users get started quickly
- Maintain Quality - Review and update regularly
Validation & Testing
Before Submitting
-
Validate Front Matter:
# Check YAML syntax npm run validate -
Test File Naming:
- All lowercase: ✓
- Hyphens only: ✓
- No spaces/underscores: ✓
- Correct extension: ✓
-
Build Check:
npm run build -
Line Endings:
bash scripts/fix-line-endings.sh -
Test in Copilot:
- Load agent/prompt/instruction
- Verify it activates correctly
- Test with sample scenarios
- Validate output quality
Repository Structure
awesome-copilot/
├── agents/ # 200+ specialized agents
│ ├── python-expert.agent.md
│ ├── azure-architect.agent.md
│ └── security-reviewer.agent.md
├── prompts/ # 180+ task templates
│ ├── create-readme.prompt.md
│ ├── optimize-code.prompt.md
│ └── generate-tests.prompt.md
├── instructions/ # 150+ coding standards
│ ├── csharp.instructions.md
│ ├── react.instructions.md
│ └── terraform.instructions.md
├── collections/ # Curated groupings
│ ├── azure-devops.collection.md
│ └── security-toolkit.collection.md
├── .schemas/ # JSON schemas for validation
└── scripts/ # Build and validation tools
Available Categories
Agents (200+)
- Languages: Python, Java, C#, Go, Rust, TypeScript, PHP, Kotlin
- Frameworks: React, Next.js, Angular, .NET, Laravel, Spring Boot
- Cloud: Azure, AWS, GCP specialists and architects
- DevOps: CI/CD, IaC (Terraform, Bicep), Kubernetes
- Databases: PostgreSQL, MongoDB, SQL Server, CosmosDB
- Specialized: Security, Accessibility, Performance, AI/ML
Prompts (180+)
- Code generation and refactoring
- Testing (Jest, Pytest, JUnit, xUnit)
- Documentation (README, API docs)
- Architecture and planning
- Cloud optimization
- Data modeling
- MCP server generation
Instructions (150+)
- Language-specific standards
- Framework best practices
- DevOps patterns
- Database optimization
- Security guidelines
- Accessibility requirements
- Performance tuning
When to Use This Skill
- Creating custom GitHub Copilot agents
- Writing reusable code generation prompts
- Defining project coding standards
- Building developer productivity tools
- Customizing AI assistance for specific domains
- Organizing team development guidelines
- Contributing to awesome-copilot repository
Keywords
github copilot, custom agents, prompts, instructions, collections, ai customization, code generation, developer productivity, coding standards, best practices, mcp integration, copilot extensions, ai agents, prompt engineering, code templates, development workflows
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/github-copilot-customization-expert-mm8o52yc/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/github-copilot-customization-expert-mm8o52yc' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/github-copilot-customization-expert-mm8o52yc/download' --output '.skill-downloads/github-copilot-customization-expert-mm8o52yc/SKILL.md.part' && mv '.skill-downloads/github-copilot-customization-expert-mm8o52yc/SKILL.md.part' '.skill-downloads/github-copilot-customization-expert-mm8o52yc/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Quick Reference
Component Types
| Type | Purpose | File Extension | Access Method |
|---|---|---|---|
| Agents | Specialized AI personas | .agent.md | Select in Copilot Chat or CCA |
| Prompts | Task-specific templates | .prompt.md | /awesome-copilot <command> |
| Instructions | Auto-applying standards | .instructions.md | Automatic by file pattern |
| Collections | Curated groupings | .collection.md | Browse in Copilot extensions |
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/github-copilot-customization-expert-mm8o52yc'openskills read 'github-copilot-customization-expert-mm8o52yc'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/github-copilot-customization-expert-mm8o52yc/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.