Agent skill

dev.code-extension

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.

View SKILL.md on GitHub Repository
Stars 5
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/kevinslin/llm/tree/main/skills/dev.code-extension

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.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

kevinslin/llm

gen-notifier

Generic desktop notification skill for agents. Send desktop notifications when tasks are complete (or when user input/errors block progress). By default, assume that all jobs will require a notification unless the user says otherwise.

5 0
Explore
kevinslin/llm

learn

learn from the current session

5 0
Explore
kevinslin/llm

dev.exec-plan

This skill should be used for development tasks that require detailed technical planning with persistent documentation. Use when the task involves architectural decisions, multi-phase implementation, external dependencies, or when the user explicitly requests an execution plan.

5 0
Explore
kevinslin/llm

dendron

do not use this skill

5 0
Explore
kevinslin/llm

dev.speculate

Always use this skill to provide context on the codebase. Automatically initializes and references the Speculate documentation framework (coding rules, shortcuts, templates, and project specs) to ensure agents understand project structure, development workflows, and coding standards. Use for every task to maintain context and code quality.

5 0
Explore
kevinslin/llm

dev.code

This skill should be used when performing any coding task including implementing features, fixing bugs, refactoring code, or making any modifications to source code. Provides best practices, security considerations, testing guidelines, and a structured workflow for development tasks.

5 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results