plugin-management
Discover, evaluate, install, test, and manage agent plugins for VS Code Copilot
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Discover, evaluate, install, test, and manage agent plugins for VS Code Copilot
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create an Architectural Decision Record (ADR) to document a significant design or technology choice
Audit VS Code extensions against the current project stack and recommend keep/add/remove actions
Diagnose and fix a failing CI pipeline or GitHub Actions workflow
Triage a GitHub issue by classifying severity, labelling waste category, proposing next action, and drafting a structured response
Create a new MCP server — clarify purpose, choose transport, scaffold, implement, test, and register
Configure and manage Model Context Protocol servers for external tool access
| name | plugin-management |
| description | Discover, evaluate, install, test, and manage agent plugins for VS Code Copilot |
| compatibility | >=3.2 |
Skill metadata: version "1.0"; license MIT; tags [plugins, agents, extensions, discovery, management]; compatibility ">=3.2"; recommended tools [codebase, runCommands, editFiles].
Agent plugins (VS Code 1.110+, Preview) are installable packages that bundle agents, skills, hooks, MCP servers, and slash commands. This skill covers discovering, evaluating, installing, testing, and managing plugins alongside the template's own customization files.
User wants a plugin
│
├─ 1. CHECK INSTALLED — list installed plugins
│ Run in Extensions view: filter @agentPlugins
│ Or check VS Code settings for chat.plugins.paths (local dev plugins)
│ ├─ Found → verify it meets the need → DONE
│ └─ Not found → ↓
│
├─ 2. SEARCH — find plugins in configured marketplaces
│ Extensions view → search @agentPlugins <keyword>
│ Or browse chat.plugins.marketplaces URLs
│ ├─ Found → evaluate (see Quality Gate below) → install
│ └─ Not found → ↓
│
└─ 3. RECOMMEND ALTERNATIVE — no suitable plugin exists
Consider: workspace skill (.github/skills/), MCP server, or custom tool
Before recommending or installing a plugin, verify:
Plugins failing two or more checks are rejected.
When a plugin contributes an agent or skill with the same name as a workspace file:
| Conflict type | Resolution |
|---|---|
| Agent name collision | Workspace agent takes priority. VS Code shows source in tooltip. |
| Skill name collision | Project skills (.github/skills/) override plugin skills. |
| Hook collision | Workspace hooks fire alongside plugin hooks — check for duplicate behaviour. |
Use the Agent Debug Panel (Developer: Open Agent Debug Panel) to see exactly which agents, skills, and hooks are loaded and from which source.
| Setting | Purpose |
|---|---|
chat.plugins.enabled | Enable/disable plugin discovery (boolean) |
chat.plugins.marketplaces | URLs of Git repositories serving as plugin marketplaces |
chat.plugins.paths | Local paths for plugin development/testing |
To preview how the template's agents, skills, hooks, and prompts appear as plugin-contributed customizations:
Clone the template repo (or use an existing local copy)
Add to VS Code settings:
"chat.plugins.paths": {
"/path/to/copilot-instructions-template": true
}
Reload VS Code — plugin-contributed agents appear in the Copilot dropdown
Verify: open the Agent Debug Panel to confirm agents, skills, and hooks are loaded
Check for conflicts with any workspace-level agents in .github/agents/
@agentPlugins to see all installed plugins