winget-config-v2-to-v3 Skill
Converts WinGet Configuration files from DSC schema v0.2 (v2) to the dscv3 processor syntax (v3). Use this skill when asked to convert, migrate, or upgrade a WinGet Configuration file from v2 to v3, or when working with .winget configuration files that need to be updated to the dscv3 schema. Published by microsoft in winget-dsc.
Decision snapshot
Is this a fit?
Developers using winget-dsc, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is winget-config-v2-to-v3 Skill?
Converts WinGet Configuration files from DSC schema v0.2 (v2) to the dscv3 processor syntax (v3). Use this skill when asked to convert, migrate, or upgrade a WinGet Configuration file from v2 to v3, or when working with .winget configuration files that need to be updated to the dscv3 schema. Published by microsoft in winget-dsc. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using winget-dsc
Declared skill metadata
- Source file: samples/Convert to v3/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use winget-config-v2-to-v3 Skill
- Use it for developers using winget-dsc.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/winget-dsc
- Skill file: samples/Convert to v3/SKILL.md
What it does
Converts WinGet Configuration files from DSC schema v0.2 (v2) to the dscv3 processor syntax (v3). Use this skill when asked to convert, migrate, or upgrade a WinGet Configuration file from v2 to v3, or when working with .winget configuration files that need to be updated to the dscv3 schema.
Skill instructions
WinGet Configuration v2 → v3 Conversion Skill You are an expert at converting WinGet Configuration files from DSC schema v0.2 (v2) to the dscv3 processor syntax (v3). Follow these rules precisely. Document Structure v2 structure yaml yaml-language-server: $schema=https://aka.ms/configuration-dsc-schema/0.2 properties: configurationVersion: 0.2.0 assertions: - resource: ... resources: - resource: ... v3 structure yaml $schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json metadata: winget: processor: identifier: dscv3 resources: - type: ... Key changes: - Remove the properties: wrapper and configurationVersion - Remove assertions: section (v3 does not support assertions in the same way) - Add $schema pointing to the DSC v3 schema - Add metadata.winget.processor.identifier: dscv3 - Resources move to a top-level resources: array Field Renaming Apply these renames to every resource: | v2 Field | v3 Field | |----------|----------| | resource: | t
Verified compatibility and discovery
Frequently asked questions
What is winget-config-v2-to-v3?
winget-config-v2-to-v3 is a open-source AI agent skill with Copy skill directory. Converts WinGet Configuration files from DSC schema v0.2 (v2) to the dscv3 processor syntax (v3).
Who is winget-config-v2-to-v3 best for?
winget-config-v2-to-v3 is best for reusing agent instructions, scripts, and references.
How do I install winget-config-v2-to-v3?
Install or run winget-config-v2-to-v3 using Copy skill directory. Check winget-config-v2-to-v3 for the latest setup command.
Is winget-config-v2-to-v3 actively maintained?
winget-config-v2-to-v3 may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
