copilot-cli-configurator

Organize GitHub Copilot CLI configuration files and components into project layouts.

2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Poorgramer-Zack/copilot-cli-things --skill copilot-cli-configurator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilot-cli-configurator
Source: https://github.com/Poorgramer-Zack/copilot-cli-things/tree/main/plugins/copilot-cli-configurator/skills/copilot-cli-configurator
Command: npx skills add https://github.com/Poorgramer-Zack/copilot-cli-things --skill copilot-cli-configurator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Copilot CLI configuration and setup can be complex and error-prone when managing custom instructions (copilot-instructions.md, AGENTS.md), hooks (hooks.json), MCP servers (mcp-config.json), custom agents (.agent.md), and plugin/extension placements. This skill provides a centralized guide to organize and apply these surfaces, ensuring consistent configuration across projects.

Core Features & Use Cases

  • Centralizes setup for custom instructions, AGENTS.md, hooks.json, and mcp-config.json
  • Guides management of installed components like plugins and extensions
  • Use cases include initial config, debugging loading order, and tailoring Copilot behavior for teams

Quick Start

Follow these steps to initialize and customize Copilot CLI surfaces in your project.

Frequently Asked Questions about copilot-cli-configurator

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

FAQPage Schema
How do I configure Copilot CLI custom instructions and hooks for a project?

To configure Copilot CLI, you organize custom instructions, AGENTS.md references, hooks.json, and mcp-config.json files into your project layout. This centralizes setup to ensure consistent configuration across teams and repositories.

Where do I place mcp-config.json and hooks.json files for GitHub Copilot CLI?

You place mcp-config.json and hooks.json files according to specified project layout rules for Copilot CLI customization. Proper placement ensures the CLI correctly loads your MCP servers and executes hooks during operations.

What is the best way to organize AGENTS.md and copilot-instructions.md for teams?

Organizing AGENTS.md and copilot-instructions.md centrally ensures consistent Copilot CLI behavior across teams and repositories. This approach tailors agent instructions and manages loading order to prevent configuration conflicts.

How do I manage Copilot CLI plugins and extensions across multiple repositories?

Managing Copilot CLI plugins and extensions involves specifying their placement and applying configuration surfaces consistently across repositories. This guides when to apply each surface to maintain uniform behavior throughout your projects.

Why is my Copilot CLI configuration not loading hooks or custom agents correctly?

Copilot CLI configuration loading issues often stem from incorrect file placement for hooks.json or .agent.md files. Debugging the loading order and verifying the centralized setup of custom instructions resolves these conflicts.

Does Copilot CLI configuration require any dependencies to set up MCP servers?

Copilot CLI configuration requires no external dependencies to set up MCP servers or hooks. You only need to organize the mcp-config.json file and related configuration surfaces within your existing project layout.