How do I install the Dev.code Extension skill?

Run npx skillmds add majiayu000/dev-code-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.

Is Dev.code 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 Dev.code 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 Dev.code Extension free to use?

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

Who published Dev.code Extension?

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

Dev.code Extension by majiayu000 — Agent Skill

Name: Dev.code Extension
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

dev.code-extension

Use this skill when the user asks to install a VS Code-compatible extension into VS Code or Cursor (stable or nightly).

Input contract

Expect a local filesystem path to a .vsix file.
If the user provides a Marketplace ID instead of a path, ask for the .vsix path (unless they explicitly want Marketplace install).

Install commands (local `.vsix`)

VS Code (stable)

code --install-extension "/path/to/extension.vsix" --force
code --list-extensions --show-versions

VS Code Insiders

code-insiders --install-extension "/path/to/extension.vsix" --force
code-insiders --list-extensions --show-versions

Cursor (stable)

cursor --install-extension "/path/to/extension.vsix" --force
cursor --list-extensions --show-versions

Cursor Nightly

Prefer cursor-nightly if it’s on PATH. If not (macOS default), call it from the app bundle:

"/Applications/Cursor Nightly.app/Contents/Resources/app/bin/cursor-nightly" --install-extension "/path/to/extension.vsix" --force
"/Applications/Cursor Nightly.app/Contents/Resources/app/bin/cursor-nightly" --list-extensions --show-versions

Verification

After install, verify by grepping the extension list:
- cursor --list-extensions --show-versions | rg -n "<publisher>\\.<name>|<name>"

Automation/CI option (avoid touching a developer profile)

If the user wants isolated installs (recommended for scripts/CI), add:

--user-data-dir <dir>
--extensions-dir <dir>

Example:

cursor --user-data-dir /tmp/cursor-user --extensions-dir /tmp/cursor-ext --install-extension "/path/to/extension.vsix" --force

Sandbox note (Codex CLI)

Installing extensions writes to user/application support directories (outside the repo). In sandboxed runs, request escalated permissions for these commands.

---name: dev-code-extensiondescription: Install VS Code/Cursor extensions from a local .vsix via CLI (code, code-insiders, cursor, cursor-nightly). Use whenever asked to install an extension programmatically.--- # dev.code-extension Use this skill when the user asks to install a VS Code-compatible extension into **VS Code** or **Cursor** (stable or nightly). ## Input contract - Expect a **local filesystem path** to a `.vsix` file. - If the user provides a Marketplace ID instead of a path, ask for the `.vsix` path (unless they explicitly want Marketplace install). ## Install commands (local `.vsix`) ### VS Code (stable) ```bash code --install-extension "/path/to/extension.vsix" --force code --list-extensions --show-versions ``` ### VS Code Insiders ```bash code-insiders --install-extension "/path/to/extension.vsix" --force code-insiders --list-extensions --show-versions ``` ### Cursor (stable) ```bash cursor --install-extension "/path/to/extension.vsix" --force cursor --list-extensions --show-versions ``` ### Cursor Nightly Prefer `cursor-nightly` if it’s on PATH. If not (macOS default), call it from the app bundle: ```bash "/Applications/Cursor Nightly.app/Contents/Resources/app/bin/cursor-nightly" --install-extension "/path/to/extension.vsix" --force "/Applications/Cursor Nightly.app/Contents/Resources/app/bin/cursor-nightly" --list-extensions --show-versions ``` ## Verification - After install, verify by grepping the extension list: - `cursor --list-extensions --show-versions | rg -n "<publisher>\\.<name>|<name>"` ## Automation/CI option (avoid touching a developer profile) If the user wants isolated installs (recommended for scripts/CI), add: - `--user-data-dir <dir>` - `--extensions-dir <dir>` Example: ```bash cursor --user-data-dir /tmp/cursor-user --extensions-dir /tmp/cursor-ext --install-extension "/path/to/extension.vsix" --force ``` ## Sandbox note (Codex CLI) Installing extensions writes to user/application support directories (outside the repo). In sandboxed runs, request escalated permissions for these commands.

Frequently asked questions