create-custom-agent

Create and review VS Code custom agent .agent.md files with correct frontmatter.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Binh230199/ai --skill create-custom-agent-binh230199
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-custom-agent
Source: https://github.com/Binh230199/ai/tree/main/.github/skills/create-custom-agent
Command: npx skills add https://github.com/Binh230199/ai --skill create-custom-agent-binh230199

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a VS Code custom agent can be easy to misconfigure because the file format, frontmatter fields, tool access, and handoff behavior all need to line up for Copilot to recognize it correctly. This Skill gives you a clear authoring guide so you can build agents that behave consistently and are easy to discover.

Core Features & Use Cases

  • Defines the required frontmatter fields for .agent.md files, including name, description, tools, model, user-invocable, disable-model-invocation, and handoffs.
  • Explains where to place workspace and personal agents, how to keep tool access minimal, and how to decide whether an agent should be read-only or able to write files.
  • Helps with common use cases such as security reviewers, planners, architects, implementation agents, and other persistent personas that need consistent behavior across conversations.

Quick Start

Ask the AI to draft or review a VS Code custom agent for your role, then specify the agent name and the behavior you want it to enforce.

Frequently Asked Questions about create-custom-agent

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

FAQPage Schema
How do I create a custom agent in VS Code for GitHub Copilot?

To create a custom agent in VS Code, you need a `.agent.md` file with specific frontmatter fields like `name`, `description`, and `tools`. This ensures Copilot recognizes and correctly invokes the agent for your designated tasks.

What frontmatter fields are required for a VS Code .agent.md file?

Required frontmatter fields for an `.agent.md` file include `name` and `description`, while optional fields are `model`, `tools`, `user-invocable`, `disable-model-invocation`, and `handoffs` for configuring least-privilege access and agent routing.

How do I configure tool restrictions for custom agents in Copilot?

Configuring tool restrictions involves setting the `tools` array in the `.agent.md` frontmatter to enforce least-privilege access. You decide whether an agent should be read-only or have file-writing permissions based on its role.

Can I set up agent handoffs in GitHub Copilot for VS Code?

Yes, you can set up agent handoffs using the optional `handoffs` field in the `.agent.md` frontmatter. This formats persistent personas like planners or security reviewers to reliably route tasks to each other.

Where should I place workspace and personal custom agent files?

Workspace agents are placed in the shared workspace directory for team access, while personal agents go in your user-level settings. Correct placement ensures reliable discovery by GitHub Copilot in VS Code.

Why does my VS Code custom agent fail to trigger in Copilot?

Custom agents fail to trigger when the `.agent.md` file is misconfigured, such as missing required frontmatter fields or incorrect tool access permissions. Reviewing the file structure ensures Copilot discovers and uses it reliably.