What problem does it solve?
Building a custom GitHub Copilot agent involves choosing between declarative prompt files, VS Code extension chat participants, and GitHub App Copilot Extensions, each with different configuration formats and pitfalls. This Skill guides you through selecting the right agent type and scaffolding it correctly.
Core Features & Use Cases
- Declarative Agent Scaffolding: Generate
.github/agents/<name>.md prompt files with valid frontmatter fields like name, description, tools, model, and handoffs.
- Extension-Based Chat Participants: Implement VS Code chat participants in TypeScript with request handlers, tool calling, and package.json contribution points.
- Validation Checklist: Verify naming rules, tool availability, handoff targets, and avoid conflicts with built-in agents like @workspace.
- Use Case: You want an @-invokable Copilot agent that answers questions about your internal API. Use this Skill to scaffold a declarative agent with a scoped system prompt, restricted read-only tools, and a handoff to an implementation agent.
Quick Start
Create a custom GitHub Copilot agent named api-expert that answers questions about our REST API using only search and codebase tools.