vscode-extension Skill
Use when investigating, developing, debugging, testing, or reviewing Aspire VS Code extension behavior under extension/, including extension UI, command, debugger, RPC, DCP, MCP, and CLI-integration issues or features. Published by microsoft in aspire.
Decision snapshot
Is this a fit?
Testing, Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
9 days ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is vscode-extension Skill?
Use when investigating, developing, debugging, testing, or reviewing Aspire VS Code extension behavior under extension/, including extension UI, command, debugger, RPC, DCP, MCP, and CLI-integration issues or features. Published by microsoft in aspire. 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
- Testing
- Design and media
- Testing use cases
- Design and media use cases
Declared skill metadata
- Source file: .agents/skills/vscode-extension/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 vscode-extension Skill
- Use it for testing.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/aspire
- Skill file: .agents/skills/vscode-extension/SKILL.md
What it does
Use when investigating, developing, debugging, testing, or reviewing Aspire VS Code extension behavior under extension/, including extension UI, command, debugger, RPC, DCP, MCP, and CLI-integration issues or features.
Skill instructions
Aspire VS Code Extension This skill covers working on the Aspire VS Code extension, which lives entirely under extension/. It is a TypeScript extension built with yarn (pinned via packageManager in extension/package.json) and webpack, and it communicates with the Aspire CLI over RPC. Orientation All commands below are run from the extension/ directory unless noted. | Path | What it is | |------|------------| | extension/src/extension.ts | Activation entry point | | extension/src/commands/ | Command implementations | | extension/src/views/ | Tree views, welcome views, panel UI | | extension/src/debugger/ | Debug adapter + per-language debuggers (dotnet, node, python, go) | | extension/src/server/, extension/src/mcp/, extension/src/dcp/ | RPC server, MCP provider, DCP integration | | extension/src/loc/strings.ts | Localized strings (TypeScript-side) | | extension/package.nls.json | Localized strings referenced from package.json (%key%) | | extension/src/test/ | Mocha unit tests (.test.ts
Verified compatibility and discovery
Frequently asked questions
What is vscode-extension?
vscode-extension is a open-source AI agent skill with Copy skill directory. Use when investigating, developing, debugging, testing, or reviewing Aspire VS Code extension behavior under extension/, including extension UI, command, debugger, RPC, DCP, MCP, and CLI-integration.
Who is vscode-extension best for?
vscode-extension is best for reusing agent instructions, scripts, and references, testing workflows, design and media workflows.
How do I install vscode-extension?
Install or run vscode-extension using Copy skill directory. Check vscode-extension for the latest setup command.
Is vscode-extension actively maintained?
vscode-extension 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.
