# Dev.code Extension

> Dev.code Extension is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

- Skill name: `dev.code-extension`
- Category: [Apps & Automation](https://www.openparable.com/skill/apps-automation/1)
- Source: https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/development/devcode-extension/SKILL.md
- Repository: majiayu000/claude-skill-registry (498 GitHub stars when collected)

## SKILL.md

# 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.

---

Source: https://www.openparable.com/skill/apps-automation/dev-code-extension (OpenParable). Cite the canonical URL above.
