create-prompt
microsoft/vscode/extensions/copilot/assets/prompts/skills/create-prompt/SKILL.md
Create a reusable prompt file (.prompt.md) for a common task.
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
microsoft/vscode/extensions/copilot/assets/prompts/skills/create-prompt/SKILL.md
Create a reusable prompt file (.prompt.md) for a common task.
microsoft/vscode/extensions/copilot/assets/prompts/skills/create-skill/SKILL.md
Create a reusable skill (SKILL.md) that packages a workflow.
microsoft/vscode/extensions/copilot/assets/prompts/skills/get-search-view-results/SKILL.md
Get the current search results from the Search view in VS Code
microsoft/vscode/extensions/copilot/assets/prompts/skills/init/SKILL.md
Generate or update chat customization files for AI coding agents
microsoft/vscode/extensions/copilot/assets/prompts/skills/install-vscode-extension/SKILL.md
How to install a VS Code extension from an extension ID. Useful when the user wants to add new capabilities to their VS Code environment by installing extensions.
microsoft/vscode/extensions/copilot/assets/prompts/skills/project-setup-info-context7/SKILL.md
Comprehensive setup steps to help the user create complete project structures in a VS Code workspace. This tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: when the user wants to create a new complete project from scratch; when setting up entire project frameworks (TypeScript projects, React apps, Node.js servers, etc.); when initializing Model Context Protocol (MCP) servers with full structure; when creating VS Code extensions with proper scaffolding; when setting up Next.js, Vite, or other framework-based projects; when the user asks for \"new project\", \"create a workspace\", or \"set up a [framework] project\"; when you need to establish a complete development environment with dependencies, config files, and folder structure. When NOT to use this tool: when creating single files or small code snippets; when adding individual files to existing projects; when making modifications to existing codebases; when the user asks to \"create a file\" or \"add a component\"; for simple code examples or demonstrations; for debugging or fixing existing code. This tool provides complete project setup including folder structure creation, package.json and dependency management, configuration files (tsconfig, eslint, etc.), initial boilerplate code, development environment setup, and build and run instructions. Use other file creation tools for individual files within existing projects.
microsoft/vscode/extensions/copilot/assets/prompts/skills/project-setup-info-local/SKILL.md
Comprehensive setup steps to help the user create complete project structures in a VS Code workspace; this tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: user wants to create a new complete project from scratch; setting up entire project frameworks (TypeScript projects, React apps, Node.js servers, etc.); initializing Model Context Protocol (MCP) servers with full structure; creating VS Code extensions with proper scaffolding; setting up Next.js, Vite, or other framework-based projects; user asks for "new project", "create a workspace", "set up a [framework] project"; need to establish a complete development environment with dependencies, config files, and folder structure. When NOT to use this tool: creating single files or small code snippets; adding individual files to existing projects; making modifications to existing codebases; user asks to "create a file" or "add a component"; simple code examples or demonstrations; debugging or fixing existing code. This tool provides complete project setup including: folder structure creation; package.json and dependency management; configuration files (tsconfig, eslint, etc.); initial boilerplate code; development environment setup; build and run instructions. Use other file creation tools for individual files within existing projects.
microsoft/vscode/extensions/copilot/assets/prompts/skills/troubleshoot/SKILL.md
Investigate unexpected chat agent behavior by analyzing direct debug logs in JSONL files. Use when users ask why something happened, why a request was slow, why tools or subagents were used or skipped, or why instructions/skills/agents did not load.
microsoft/vscode/.github/skills/accessibility/SKILL.md
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
microsoft/vscode/.github/skills/agent-host-chat-contributions/SKILL.md
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
microsoft/vscode/.github/skills/agent-host-e2e-tests/SKILL.md
Use when writing, recording, updating, validating, or troubleshooting Agent Host end-to-end and real-provider integration tests under src/vs/platform/agentHost/test/node/e2e and providerIntegration. Covers adding a cross-provider test, re-recording fixtures after an SDK bump, required cross-platform Azure validation, gating non-deterministic or platform-specific tests, and diagnosing replay cache misses.
microsoft/vscode/.github/skills/agent-host-logs/SKILL.md
Analyze Agent Host debug log exports. Use when given an ah-logs or ahp-logs zip/folder, an Export Agent Host Debug Logs bundle, events.jsonl, AHP JSONL transport logs, Agent Host.log, remote-agenthost.log, or copilot-logs.
microsoft/vscode/.github/skills/author-contributions/SKILL.md
Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.
microsoft/vscode/.github/skills/auto-perf-optimize/SKILL.md
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
microsoft/vscode/.github/skills/azure-pipelines/SKILL.md
Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.
microsoft/vscode/.github/skills/build-champ-triage/SKILL.md
Find out why a build has failed
microsoft/vscode/.github/skills/chat-customizations-editor/SKILL.md
Use when working on the Chat Customizations editor — the management UI for agents, skills, instructions, hooks, prompts, MCP servers, and plugins.
microsoft/vscode/.github/skills/chat-perf/SKILL.md
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
microsoft/vscode/.github/skills/chat-pet-sprite-creation/SKILL.md
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
microsoft/vscode/.github/skills/codenotify/SKILL.md
codenotify
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.