Skill rating
79 skills. The A–F grade combines safety (60%) and quality (40%); tests add a bonus. The rating refreshes automatically from open catalogs.
ManufacturingLogistics and warehouseProcurementQuality controlContact centreField serviceFinanceCustomer supportindustry shortcuts
| # | Grade | Skill | Score ▾ | Safety | Quality | Process | Tests | Popularity | Updated |
|---|---|---|---|---|---|---|---|---|---|
| 51 | C | Create a custom agent (.agent.md) for a specific job. | 100 | 65 | C | — | ★ 193 511 | 4 h ago | |
| 52 | C | Create a reusable skill (SKILL.md) that packages a workflow. | 100 | 65 | C | — | ★ 193 511 | 4 h ago | |
| 53 | C | Create a hook (.json) to enforce policy or automate agent lifecycle events. | 100 | 65 | C | — | ★ 193 511 | 4 h ago | |
| 54 | C | codenotify | 100 | 64 | D | — | ★ 193 511 | 4 h ago | |
| 55 | C | Help author a component specification for an agent. | 100 | 65 | C | — | ★ 193 511 | 4 h ago | |
| 56 | C | Core principles and workflow router for changes to the Agents Window under src/vs/sessions. | 100 | 65 | D | — | ★ 193 511 | 4 h ago | |
| 57 | C | Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. U | 95 | 69 | C | — | ★ 193 511 | 4 h ago | |
| 58 | C | Get the current search results from the Search view in VS Code | 100 | 61 | C | — | ★ 193 511 | 4 h ago | |
| 59 | C | Generate or update chat customization files for AI coding agents | 100 | 61 | C | — | ★ 193 511 | 4 h ago | |
| 60 | C | Update doc comments | 100 | 61 | D | — | ★ 193 511 | 4 h ago | |
| 61 | C | Find out why a build has failed | 100 | 57 | C | — | ★ 193 511 | 4 h ago | |
| 62 | B | Use when adding, changing, or reviewing a VS Code A/B experiment, either an experiment-controlled setting or a treatment read with the assignment service, and when deciding whether and where to log an | 100 | 82 | C missing files | — | ★ 193 511 | 4 h ago | |
| 63 | C | 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 | 100 | 54 | C | — | ★ 193 511 | 4 h ago | |
| 64 | B | 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. C | 100 | 78 | D missing files | — | ★ 193 511 | 4 h ago | |
| 65 | C | update-instructions | 100 | 53 | D | — | ★ 193 511 | 4 h ago | |
| 66 | C | First Time Setup | 100 | 52 | D | — | ★ 193 511 | 4 h ago | |
| 67 | C | Group similar issues. | 100 | 53 | D | — | ★ 193 511 | 4 h ago | |
| 68 | B | 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 w | 100 | 74 | D missing files | — | ★ 193 511 | 4 h ago | |
| 69 | B | Use when running integration tests in the VS Code repo. Covers scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows), their supported arguments for filtering, and the di | 100 | 75 | D missing files | — | ★ 193 511 | 4 h ago | |
| 70 | C | 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 | 77 | 84 | C | — | ★ 193 511 | 4 h ago | |
| 71 | B | Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down f | 100 | 75 | D missing files | — | ★ 193 511 | 4 h ago | |
| 72 | B | OpenTelemetry guidance for VS Code agent experiences. Use when changing Agent Host telemetry, local Copilot Chat telemetry, provider-native spans or metrics, OTel settings and managed policy, trace pe | 100 | 75 | D missing files | — | ★ 193 511 | 4 h ago | |
| 73 | C | ci-artifact-testingAnalyzerGitHubVS CodeSoftware developmentData and analyticsmicrosoft/vscodeAgent Skills Use when validating an upstream pull request or dependency fix against VS Code tests using GitHub Actions CI build artifacts instead of building locally. Covers finding compatible binaries, verifying | 100 | 72 | D missing files | — | ★ 193 511 | 4 h ago | |
| 74 | C | Update the committed blocks-ci screenshot hashes after the "Screenshots & Tests" check fails, or investigate a screenshot diff reported on a PR. Use when asked to update, accept, or refresh component | 100 | 72 | F missing files | — | ★ 193 511 | 4 h ago | |
| 75 | C | Use when adding, reviewing, or troubleshooting an interactive release-note Try This experience, including commands, views, editor samples, Chat drafts, guided spotlights, prerequisites, scoped targets | 100 | 72 | D missing files | — | ★ 193 511 | 4 h ago | |
| 76 | C | Use when running unit tests in the VS Code repo. Covers the runTests tool, scripts/test.sh (macOS/Linux) and scripts/test.bat (Windows), and their supported arguments for filtering, globbing, and debu | 100 | 72 | D missing files | — | ★ 193 511 | 4 h ago | |
| 77 | C | 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 ch | 100 | 72 | F missing files | — | ★ 193 511 | 4 h ago | |
| 78 | D | fixIssueNo | 100 | 35 | D | — | ★ 193 511 | 4 h ago | |
| 79 | C | The VS Code design philosophy — a shared Values→Principles→Moves vocabulary for reasoning about UI in design terms instead of raw pixels. Use when designing, building, reviewing, or giving feedback on | 100 | 53 | F missing files | — | ★ 193 511 | 4 h ago |