github-copilot-plugins

Designs, validates, and packages GitHub Copilot and Agent Plugins for Visual Studio Code.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/schattenspiegel/skill-foundry-skills --skill github-copilot-plugins-schattenspiegel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-copilot-plugins
Source: https://github.com/schattenspiegel/skill-foundry-skills/tree/main/skills/github-copilot-plugins
Command: npx skills add https://github.com/schattenspiegel/skill-foundry-skills --skill github-copilot-plugins-schattenspiegel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Bundling skills, MCP servers, agents, hooks, and commands into a distributable VS Code plugin requires choosing the right manifest format, validating every component, and handling trust and lifecycle correctly, which is error-prone without guidance. ## Core Features & Use Cases - Format Selection: Chooses between portable Agent Plugins 1.0 (plugin.json, skills/, mcp.json) and client-specific Copilot/Claude formats based on required components. - Component Validation: Verifies manifests, MCP servers, hooks, agents, commands, versions, licenses, and root tokens before packaging. - Trust & Lifecycle Review: Ensures executable behavior, writable state locations, and install/disable/update/uninstall behavior are inspected and documented. - Use Case: A team wants to ship three reviewed skills plus an MCP server as one versioned VS Code plugin; this Skill guides manifest authoring, portability decisions, and pre-install verification. ## Quick Start Ask the assistant to design and validate an Agent Plugins 1.0 bundle containing your skills directory and mcp.json for distribution in VS Code.

Frequently Asked Questions about github-copilot-plugins

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

FAQPage Schema
How do I create a GitHub Copilot plugin for VS Code?▼

Define the bundle's user job, components, license, and update path, then author a root plugin.json following the Agent Plugins 1.0 schema with skills under skills/ and MCP definitions in mcp.json. Validate every component and test install, disable, and uninstall before distribution.

What is the Agent Plugins 1.0 plugin.json format?▼

Agent Plugins 1.0 uses a root plugin.json with the schema URL https://agent-plugins.org/schemas/1.0.0/plugin.schema.json, a required name field, and optional version, description, author, license, and keywords. Skills are discovered under skills/ and MCP servers under mcp.json.

When should I use a plugin instead of a single skill?▼

Use a plugin only when multiple components genuinely share installation, versioning, trust, and lifecycle. For one standalone skill, a plain skill repository is simpler and avoids unnecessary packaging overhead.

Are agents, hooks, and slash commands portable across plugin formats?▼

No. Agent Plugins 1.0 portable components are skills and MCP servers only. Agents, hooks, and slash commands are client-specific, so using them requires a host-specific Copilot or Claude format and documenting the lost portability.

What should I check before installing a Copilot plugin?▼

Inspect the full package contents, validate manifest and MCP JSON, verify executable provenance, licenses, and absence of secrets, then test enable, disable, update, and uninstall behavior. Never install an unreviewed plugin or assume trust persists.