GitHub Copilot Guide: Plugin Packaging for Agents, Skills, and Hooks

InYourLeague Research · 2026-08-27

Answer in brief

The supplied excerpt verifies that GitHub Docs contains an “About GitHub Copilot plugins” page and navigation entries concerning plugin creation, installation, marketplaces, enterprise standards, custom agents, agent skills, hooks, MCP, and plugin directories. Because the excerpt consists mainly of navigation text, it does not establish package schemas, relationships among those topics, runtime behavior, distribution requirements, or a selectable model ID.

Key facts at a glance

Failure modes and verification

FAQ

What can be stated confidently from the supplied evidence?

The supplied official excerpt shows an “About GitHub Copilot plugins” page and navigation entries concerning plugins, custom agents, agent skills, hooks, MCP, installation, marketplaces, and enterprise standards. It does not explain the behavior behind those entries.

Can custom agents, agent skills, hooks, and MCP be described as plugin components?

Not from this excerpt alone. Their appearance in the same broader documentation navigation does not establish that they share a package format or can be included in a plugin.

Can the draft provide a plugin manifest name or directory tree?

No. The excerpt contains no manifest filename, required path, field schema, validation rule, discovery rule, or precedence rule.

What does the excerpt establish about hooks?

It shows navigation labels including Pre Tool Use, Post Tool Use, Session Lifecycle, User Prompt Submitted, and user-prompt transformation. It does not establish that these are literal configuration identifiers or specify their payload and execution contracts.

What does the excerpt establish about MCP?

It shows documentation navigation concerning MCP servers, toolsets, registries, and debugging. It does not explain whether MCP configuration is packaged in a plugin or provide a configuration schema.

Does the evidence prove that plugin distribution is declarative or that no selectable model ID exists?

No. The excerpt does not specify a declarative distribution format or a selectable model ID, but neither omission proves that GitHub provides no such information elsewhere.

Sources and freshness

• Official source
• Last verified: 2026-08-27

Extended guide

Evidence scope

Verified on August 27, 2026, using only GitHub’s official About GitHub Copilot plugins page excerpt supplied for this review. The excerpt establishes the page title and the presence of related navigation labels. It does not include the explanatory content of the plugin overview or the linked instructional pages.

This distinction matters because nearby entries in a documentation menu do not, by themselves, prove that the corresponding features are packaged together. The excerpt does not explain whether custom agents, agent skills, hooks, MCP integrations, or plugin directories are components of one plugin format, separate customization mechanisms, SDK features, or concepts that overlap only in some environments.

Evidence map

Publication guidance

1. Describe the evidence at the level it supports. It is safe to say that GitHub’s documentation navigation contains the named topics. Do not turn those labels into claims about supported behavior without the content of the relevant official page.

2. Keep the component relationship open. Avoid statements such as “a plugin packages agents, skills, hooks, and MCP.” A supported alternative is: “GitHub Docs lists plugins, custom agents, agent skills, hooks, and MCP as topics; consult their dedicated pages to determine whether and how they connect.”

3. Do not invent a package tree. No manifest filename, directory name, required field, discovery rule, or precedence rule is visible in the excerpt. Examples containing such details should be withheld until direct official evidence is available.

4. Treat hook details as verification questions. Before publishing hook instructions, determine from the dedicated documentation whether the visible labels are literal event names and, if applicable, verify payloads, execution rules, ordering, timeouts, and failure handling.

5. Treat MCP details conditionally. If a dedicated page states that plugins may declare MCP servers, record only the documented configuration fields, transports, authentication options, permissions, and supported hosts. The supplied excerpt does not answer those questions.

6. Do not assume declarative distribution. The marketplace and installation labels show that those documentation topics exist, but they do not reveal a declarative format. Verify any manifest, metadata, repository, publishing, enterprise-policy, or approval requirement before describing a distribution workflow.

Evidence gate checklist

• A direct official passage defines what a GitHub Copilot plugin is.
• Official instructions establish any required package paths and fields.
• Direct evidence explains whether agents, skills, hooks, or MCP can be included.
• Hook and MCP contracts are supported by their dedicated official pages.
• Installation and marketplace claims are supported beyond navigation labels.
• Enterprise requirements are stated only when an official page makes them applicable.
• Model information is limited to what the cited source actually says.

The supplied excerpt does not specify a selectable model ID. This is an excerpt-scoped limitation, not evidence that GitHub publishes no model information elsewhere.

Model availability note: The official source does not specify a selectable model ID.