vssdk-sdk-style-conversion Skill
Converts Visual Studio extension (VSIX/VSSDK) projects from legacy project format to SDK-style. Handles VSSDK-specific concerns including package references, VSIX manifest, VSCT command tables, project capabilities, and solution deploy markers for F5 debugging. Use when asked to "convert VSIX to SDK style", "modernize Published by microsoft in upgrade-agent-plugins.
What is vssdk-sdk-style-conversion Skill?
Converts Visual Studio extension (VSIX/VSSDK) projects from legacy project format to SDK-style. Handles VSSDK-specific concerns including package references, VSIX manifest, VSCT command tables, project capabilities, and solution deploy markers for F5 debugging. Use when asked to "convert VSIX to SDK style", "modernize Published by microsoft in upgrade-agent-plugins. 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.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Deployment
- Deployment use cases
Technical details
- Install or run with Copy skill directory
When to use vssdk-sdk-style-conversion Skill
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/scenarios/vssdk-sdk-style-conversion/SKILL.md
What it does
Converts Visual Studio extension (VSIX/VSSDK) projects from legacy project format to SDK-style. Handles VSSDK-specific concerns including package references, VSIX manifest, VSCT command tables, project capabilities, and solution deploy markers for F5 debugging. Use when asked to "convert VSIX to SDK style", "modernize
Skill instructions
VSSDK SDK-Style Conversion Convert Visual Studio extension projects from legacy (old-style) format to modern SDK-style while preserving VSIX packaging, F5 debugging, and extension functionality. Related skills: - converting-to-sdk-style — base SDK-style conversion mechanics (used during execution) - sdk-style-conversion — general SDK-style conversion scenario (for non-VSIX projects) - managing-package-references — NuGet package management Workflow Stages Run these stages in order: 1. Assessment — Analyze the VSIX project structure and risks. Creates assessment.md. 2. Planning — Create the conversion plan with VSSDK specifics. Creates plan.md. 3. Execution — Convert the project and apply the VSSDK overlay. Modifies the project file and solution file. 4. Validation — Build, verify the VSIX output, and check deploy markers. 1. Assessment Analyze the VSIX project to understand its structure and identify conversion considerations. What to Capture | Aspect | Where to Look | Why It Matters |
Explore related resources
Frequently asked questions
What is vssdk-sdk-style-conversion?
vssdk-sdk-style-conversion is a open-source AI agent skill with Copy skill directory. Converts Visual Studio extension (VSIX/VSSDK) projects from legacy project format to SDK-style.
Who is vssdk-sdk-style-conversion best for?
vssdk-sdk-style-conversion is best for reusing agent instructions, scripts, and references, deployment workflows.
How do I install vssdk-sdk-style-conversion?
Install or run vssdk-sdk-style-conversion using Copy skill directory. Check vssdk-sdk-style-conversion for the latest setup command.
Is vssdk-sdk-style-conversion actively maintained?
vssdk-sdk-style-conversion may need a closer maintenance check before production use.
Auto-fetched from GitHub.
