What problem does it solve?
Cursor and Kiro IDEs do not support extensions from the Visual Studio Marketplace, requiring developers to publish to Open VSX separately to make their VS Code extensions available to users of those editors. This Skill eliminates the confusion around Open VSX setup, namespace verification, and cross-registry publishing workflows that often block smooth extension deployment.
Core Features & Use Cases
- Open VSX Setup Guidance: Walks through one-time configuration including OVSX_PAT token creation, namespace ownership verification, and Eclipse Foundation review requirements for new publishers.
- End-to-End Publishing Workflow: Covers pre-publish validation, correct VSIX file selection, step-by-step publish commands, and simultaneous publishing to both VS Marketplace and Open VSX.
- Troubleshooting & Cross-Links: Includes a dedicated common errors table for issues like unverified namespaces, wrong VSIX uploads, and version conflicts, plus hand-offs to related skills for packaging, CI pipelines, and cross-platform scripting.
- Use Case: If you have built a VS Code extension and need to make it available to Cursor and Kiro users without manual VSIX distribution, this Skill provides the complete, tested workflow to publish and maintain your extension on Open VSX.
Quick Start
Use the cursor-kiro-extension-publishing skill to publish your packaged VS Code extension VSIX to Open VSX so it is available for installation in Cursor and Kiro IDEs.
