How do I install the Build Extension skill?

Run npx skillmds add majiayu000/build-extension in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Build Extension skill do?

Build, test, and package VSCode extensions in the dart_node repo It is listed under Coding & Dev Tools on SkillMD.

Is Build Extension safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Build Extension?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Build Extension free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Build Extension?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Build Extension by majiayu000 — Agent Skill

Name: Build Extension
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Build VSCode Extensions

This repo has two VSCode extension components:

Component	Location	What it is
dart_node_vsix	`packages/dart_node_vsix/`	The SDK package — Dart bindings for the VSCode extension API (commands, tree views, webviews, status bar, etc.)
too_many_cooks	`examples/too_many_cooks_vscode_extension/`	A concrete extension built with that SDK — multi-agent coordination UI

too-many-cooks extension

Full build (MCP server + extension + .vsix package):

bash examples/too_many_cooks_vscode_extension/build.sh

This does:

Compiles MCP server: dart compile js → add_preamble.dart → server_node.js
Compiles extension: dart compile js → wrap-extension.js bridge → out/lib/extension.js
Packages: vsce package → .vsix file

Test (runs Mocha tests under a real VSCode instance):

cd examples/too_many_cooks_vscode_extension && npm run pretest && npm test

On headless Linux, prefix with xvfb-run -a.

Install into VSCode:

code --install-extension examples/too_many_cooks_vscode_extension/*.vsix

dart_node_vsix SDK package

Test the SDK (Dart tests compiled to JS, run in VSCode):

cd packages/dart_node_vsix && npm install && npm run compile && npm test

What it provides — Dart bindings for:

commands, window, workspace, statusBar
TreeView, Webview, OutputChannel
ExtensionContext, Disposable
Mocha test API bindings
JS interop helpers (Promise, EventEmitter)

Architecture

Both use the same pattern: Dart → dart compile js → wrapper script → VSCode-compatible JS module.

The wrapper scripts (scripts/wrap-extension.js, scripts/wrap-tests.js) bridge dart2js output to VSCode's CommonJS require/module.exports system and inject polyfills (navigator, self) needed by dart2js async scheduling.

---name: build-extensiondescription: Build, test, and package VSCode extensions in the dart_node repo--- # Build VSCode Extensions This repo has two VSCode extension components: | Component | Location | What it is | |-----------|----------|------------| | **dart_node_vsix** | `packages/dart_node_vsix/` | The SDK package — Dart bindings for the VSCode extension API (commands, tree views, webviews, status bar, etc.) | | **too_many_cooks** | `examples/too_many_cooks_vscode_extension/` | A concrete extension built with that SDK — multi-agent coordination UI | ## too-many-cooks extension **Full build** (MCP server + extension + .vsix package): ```bash bash examples/too_many_cooks_vscode_extension/build.sh ``` This does: 1. Compiles MCP server: `dart compile js` → `add_preamble.dart` → `server_node.js` 2. Compiles extension: `dart compile js` → `wrap-extension.js` bridge → `out/lib/extension.js` 3. Packages: `vsce package` → `.vsix` file **Test** (runs Mocha tests under a real VSCode instance): ```bash cd examples/too_many_cooks_vscode_extension && npm run pretest && npm test ``` On headless Linux, prefix with `xvfb-run -a`. **Install into VSCode**: ```bash code --install-extension examples/too_many_cooks_vscode_extension/*.vsix ``` ## dart_node_vsix SDK package **Test the SDK** (Dart tests compiled to JS, run in VSCode): ```bash cd packages/dart_node_vsix && npm install && npm run compile && npm test ``` **What it provides** — Dart bindings for: - `commands`, `window`, `workspace`, `statusBar` - `TreeView`, `Webview`, `OutputChannel` - `ExtensionContext`, `Disposable` - `Mocha` test API bindings - JS interop helpers (`Promise`, `EventEmitter`) ## Architecture Both use the same pattern: Dart → `dart compile js` → wrapper script → VSCode-compatible JS module. The wrapper scripts (`scripts/wrap-extension.js`, `scripts/wrap-tests.js`) bridge dart2js output to VSCode's CommonJS `require`/`module.exports` system and inject polyfills (navigator, self) needed by dart2js async scheduling.

Frequently asked questions