add-policy
Guides the complete VS Code configuration-policy lifecycle, including registration, validation, export, extension policies, preview flags, and managed settings.
Install
mkdir -p .claude/skills/add-policy && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10483" && unzip -o skill.zip -d .claude/skills/add-policy && rm skill.zipInstalls to .claude/skills/add-policy
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.Key capabilities
- →Registers policy metadata and PolicyCategory values on VS Code configuration properties
- →Validates policy changes and exports Windows, macOS, and Linux policy artifacts
- →Defines extension policies through distro configuration and test fixtures
- →Adds managed GitHub Preview feature flags
- →Handles layered enterprise settings and shared policyReference definitions
How it works
The workflow updates the configuration registration, checks PolicyCategory imports, compiles the affected TypeScript, and runs the policy export tooling. Specialized sections cover extension policies, preview-feature flags, managed-setting precedence, and shared policy references.
Inputs & outputs
When to use add-policy
- →Registering and exporting a new native VS Code configuration policy
- →Adding enterprise policy support for an extension-provided setting
- →Controlling a GitHub Preview feature with managed policy
- →Supporting native MDM, GitHub server, and file-based managed settings
- →Applying one policy definition to several settings with policyReference
About add-policy
Explains how to add policy metadata to VS Code settings, validate the TypeScript changes, and export platform policy artifacts. It also covers extension-provided policies, GitHub Preview feature flags, enterprise managed settings, and policy references shared by multiple settings.
Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.
When not to use it
- →For ordinary settings that do not need administrator-enforced policy
- →For editing generated policy artifacts directly instead of their source definitions
Prerequisites
Limitations
- →The file paths and commands are specific to the Microsoft VS Code repository
- →Generated policy files must be refreshed through the documented export commands
- →Repository behavior may change when the upstream policy architecture changes
How it compares
This is the maintained VS Code repository workflow, grounded in the actual policy registry, export scripts, distro schema, and managed-settings implementation rather than a generic enterprise-policy checklist.
Compared to similar skills
add-policy side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| add-policy (this skill) | 0 | 1mo | Review | Advanced |
| nestjs-expert | 37 | 6mo | Review | Advanced |
| zod-4 | 12 | 7mo | No flags | Intermediate |
| develop-ai-functions-example | 5 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by microsoft
View all by microsoft →You might also like
nestjs-expert
davila7
Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js authentication. Use PROACTIVELY for any Nest.js application issues including architecture decisions, testing strategies, performance optimization, or debugging complex dependency injection problems. If a specialized expert is a better fit, I will recommend switching and stop.
zod-4
prowler-cloud
Zod 4 schema validation patterns. Trigger: When creating or updating Zod v4 schemas for validation/parsing (forms, request payloads, adapters), including v3 -> v4 migration patterns.
develop-ai-functions-example
vercel
Develop examples for AI SDK functions. Use when creating, running, or modifying examples under examples/ai-functions/src to validate provider support, demonstrate features, or create test fixtures.
effect-patterns-project-setup--execution
PaulJPhilp
Effect-TS patterns for Project Setup Execution. Use when working with project setup execution in Effect-TS applications.
monorepo-structure
dadbodgeoff
Set up a Turborepo + pnpm monorepo for sharing code between frontend, backend, and workers. One repo, multiple packages, shared types, parallel builds.
indicator-buffer
DaveSkender
Implement BufferList incremental indicators with efficient state management. Use for IIncrementFromChain or IIncrementFromQuote implementations. Covers interface selection, constructor patterns, and BufferListTestBase testing requirements.