How do I install the Github Copilot Plugins skill?

Run npx skillmds@latest add schattenspiegel/github-copilot-plugins in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Copilot Plugins safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Copilot Plugins?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Copilot Plugins free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Copilot Plugins?

schattenspiegel (@schattenspiegel) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Copilot Plugins by schattenspiegel

Name: Github Copilot Plugins
Rating: 4.2 (5 reviews)
Author: schattenspiegel

Github Copilot Plugins

Use for designing, creating, reviewing, or packaging GitHub Copilot and Agent Plugins for Visual Studio Code, including plugin.json, portable skills, MCP components, client-specific agents, commands, and hooks. Do not use for a single standalone skill, ordinary VS Code extensions, or installing an unreviewed plugin.

schattenspiegel Updated Aug 19, 2026 0 repo stars

File contents

GitHub Copilot plugins

Plugins are preview functionality in VS Code and can bundle executable hooks or MCP servers. Inspect the installed version and active plugin schema first. Package only components that genuinely share installation, versioning, trust, and lifecycle.

Workflow

Define the bundle's user job, component graph, portability target, license, publisher, update path, executable behavior, and uninstall contract.
Prefer Agent Plugins 1.0 for portable skills and MCP servers: root plugin.json, skills/, and mcp.json.
Use a host-specific Copilot/Claude compatibility format only when agents, hooks, or slash commands are required and document the lost portability.
Validate every embedded skill, MCP server, hook, agent, command, reference, root token, version, and license independently before packaging.
Keep writable state under the format's data location; never write into the installed package or embed credentials.
Inspect the full package before separately authorized local installation. Test enable, disable, update, and uninstall without assuming trust persists.

Rules

Do not create a plugin merely to distribute one skill; a skill repository is simpler.
Agent Plugins 1.0 portable components are skills and MCP servers. Treat agents, hooks, and slash commands as client-specific unless the active spec says otherwise.
Plugin MCP servers can be trusted as part of installation; make that expansion visible.
Never claim Microsoft/GitHub endorsement or copy vendor documentation/examples.
Pin versions and retain third-party notices for any bundled material.

Read plugin contracts, use bundle patterns, and apply verification.

Completion

The manifest and every component validate; portability claims match the chosen format; executable trust and licenses are visible; no secrets/private authoring material are bundled; and an approved VS Code smoke proves install, discovery, disable, update behavior, and clean uninstall.

---name: github-copilot-pluginsdescription: Use for designing, creating, reviewing, or packaging GitHub Copilot and Agent Plugins for Visual Studio Code, including plugin.json, portable skills, MCP components, client-specific agents, commands, and hooks. Do not use for a single standalone skill, ordinary VS Code extensions, or installing an unreviewed plugin.---# GitHub Copilot pluginsPlugins are preview functionality in VS Code and can bundle executable hooksor MCP servers. Inspect the installed version and active plugin schema first.Package only components that genuinely share installation,versioning, trust, and lifecycle.## Workflow1. Define the bundle's user job, component graph, portability target, license, publisher, update path, executable behavior, and uninstall contract.2. Prefer Agent Plugins 1.0 for portable skills and MCP servers: root `plugin.json`, `skills/`, and `mcp.json`.3. Use a host-specific Copilot/Claude compatibility format only when agents, hooks, or slash commands are required and document the lost portability.4. Validate every embedded skill, MCP server, hook, agent, command, reference, root token, version, and license independently before packaging.5. Keep writable state under the format's data location; never write into the installed package or embed credentials.6. Inspect the full package before separately authorized local installation. Test enable, disable, update, and uninstall without assuming trust persists.## Rules- Do not create a plugin merely to distribute one skill; a skill repository is simpler.- Agent Plugins 1.0 portable components are skills and MCP servers. Treat agents, hooks, and slash commands as client-specific unless the active spec says otherwise.- Plugin MCP servers can be trusted as part of installation; make that expansion visible.- Never claim Microsoft/GitHub endorsement or copy vendor documentation/examples.- Pin versions and retain third-party notices for any bundled material.Read [plugin contracts](references/artifact-contracts.md), use [bundle patterns](references/patterns.md), and apply [verification](references/verification.md).## CompletionThe manifest and every component validate; portability claims match the chosenformat; executable trust and licenses are visible; no secrets/private authoringmaterial are bundled; and an approved VS Code smoke proves install, discovery,disable, update behavior, and clean uninstall.

Frequently asked questions