Helps developers add, review, and export VS Code configuration policies.
The material indicates a prompt/documentation-style skill from an open-source repository, with no required secrets, no declared remote endpoints, and no direct execution or exfiltration capability, so overall risk is low. It does describe VS Code policy and OS-level configuration mechanisms, but based on the provided facts this is informational rather than an actual privilege-granting tool.
The material explicitly states that no secrets or environment variables are required. The README mentions account-level policy data conceptually, but does not ask for user tokens or describe credential collection, storage, or forwarding.
Both the system checks and the material indicate no remote endpoints. Although the document mentions GitHub/account policy sources as part of VS Code architecture, the skill itself does not declare network access, data upload, or transmission to third parties.
It is classified as prompt-only. The README is procedural guidance for adding/modifying configuration policies and does not show that the skill launches local processes, runs scripts, or invokes system commands.
The material does not declare direct read/write access to local files, the registry, plist, or /etc paths. These are mentioned only as part of VS Code's policy mechanisms, not as actual data-access permissions granted to the skill.
The source points to Microsoft's open-source VS Code repository on GitHub, making it auditable and a strong positive trust signal. Although the star/maintenance metadata is incomplete and the license is unspecified here, there are no red flags such as closed source, unclear distribution, or suspicious installation chains.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "add-policy" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/vscode/main/.github/skills/add-policy/SKILL.md 2. Save it as ~/.claude/skills/add-policy/SKILL.md 3. Reload skills and tell me it's ready
Please add a policy field to this VS Code setting and verify that policy registration, description updates, and export-related changes are all included.
A complete set of policy integration suggestions or code changes covering registration, validation, and export.
Please review the newly added policy setting in this configuration change and confirm whether naming, defaults, platform compatibility, and generated artifacts follow conventions.
A review report identifying missing pieces, risks, and files or steps that still need to be added.
I updated the policy definition for an existing setting. Please check whether this change affects registration, export, or platform-specific artifact generation in the policy lifecycle.
An impact analysis and recommended changes to ensure the policy update does not break the overall workflow.
Policies allow enterprise administrators to lock configuration settings via OS-level mechanisms (Windows Group Policy, macOS managed preferences, Linux config files) or via Copilot account-level policy data. This skill covers the complete procedure.
policy: field to any configuration propertyIPolicyData| Source | Implementation | How it reads policies |
|---|---|---|
| OS-level (Windows registry, macOS plist) | NativePolicyService via @vscode/policy-watcher | Watches Software\Policies\Microsoft\{productName} (Windows) or bundle identifier prefs (macOS) |
| Linux file | FilePolicyService | Reads /etc/vscode/policy.json |
| Account/GitHub | AccountPolicyService | Reads IPolicyData from IDefaultAccountService.policyData, applies value() function |
| Multiplex | MultiplexPolicyService | Combines OS-level + account policy services; used in desktop main |
| File | Purpose |
|---|---|
src/vs/base/common/policy.ts | PolicyCategory enum, IPolicy interface |
src/vs/platform/policy/common/policy.ts | IPolicyService, AbstractPolicyService, PolicyDefinition |
src/vs/platform/configuration/common/configurations.ts | PolicyConfiguration — bridges policies to configuration values |
src/vs/workbench/services/policies/common/accountPolicyService.ts | Account/GitHub-based policy evaluation |
src/vs/workbench/services/policies/common/multiplexPolicyService.ts | Combines multiple policy services |
src/vs/workbench/contrib/policyExport/electron-browser/policyExport.contribution.ts | --export-policy-data CLI handler |
src/vs/base/common/defaultAccount.ts | IPolicyData interface for account-level policy fields |
build/lib/policies/policyData.jsonc | Auto-generated policy catalog (DO NOT edit manually) |
build/lib/policies/policyGenerator.ts | Generates ADMX/ADML (Windows), plist (macOS), JSON (Linux) |
build/lib/test/policyConversion.test.ts | Tests for policy artifact generation |
policy field to the configuration propertyFind the configuration registration (typically in a *.contribution.ts file) and add a policy object to the property schema.
Required fields:
Determining minimumVersion: Always read version from the root package.json and use the major.minor portion. For example, if package.json has "version": "1.112.0", use minimumVersion: '1.112'. Never hardcode an old version like '1.99'.
policy: {
name: 'MyPolicyName', // PascalCase, unique across all policies
category: PolicyCategory.InteractiveSession, // From PolicyCategory enum
minimumVersion: '1.112', // Use major.minor from package.json version
localization: {
description: {
key: 'my.config.key', // NLS key for the description
value: nls.localize('my.config.key', "Human-readable description."),
}
}
}
Optional: value function for account-based policy:
If this policy should also be controllable via Copilot account policy data (from IPolicyData), add a value function:
policy: {
name: 'MyPolicyName',
category: PolicyCategory.InteractiveSession,
minimumVersion: '1.112', // Use major.minor from package.json version
value: (policyData) => policyData.my_field === false ? false : undefined,
localization: { /* ... */ }
}
The value function receives IPolicyData (from src/vs/base/common/defaultAccount.ts) and should:
…
Validate Azure DevOps pipeline changes and troubleshoot builds and YAML faster.
Update the GitHub Copilot CLI or SDK to a newer version.
Upgrade Anthropic SDKs, migrate versions, and fix dependency or typing issues.
Generate or update chat customization files for AI coding agents.
Find and read Code OSS dev build logs for faster debugging.
Merge session branch changes back into the base branch cleanly.
Plan retention policies and profile governance configuration for data management.
Fetch exact team policy sections efficiently for subagents using section notation.
Create hook JSON files for policy enforcement and agent lifecycle automation.
Design robust config and state file handling with safe defaults and crash recovery.
Let AI edit VS Code files with interactive diff review and change approval.
Manage AI agent configs across platforms with comparison, editing, and sync.