CtrlK
BlogDocsLog inGet started
Tessl Logo

cursor-extension-integration

Integrate VS Code extensions with Cursor IDE: compatibility, Open VSX registry, VSIX installation, conflict resolution, and essential extensions. Triggers on "cursor extensions", "cursor vscode extensions", "cursor plugins", "cursor marketplace", "open vsx", "vsix install".

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and token-efficient, with concrete commands and config blocks throughout. Its main weaknesses are monolithic structure that fails to use the provided reference bundle, and workflows (manual VSIX install, batch reinstall) that omit verification checkpoints.

Suggestions

Add verification steps to the manual VSIX and batch-reinstall workflows (e.g., confirm with `cursor --list-extensions` or check the extension activates) so batch/destructive operations include feedback loops.

Turn SKILL.md into an overview that links to the existing reference files (e.g., 'See [installing-extensions.md](references/installing-extensions.md)', '[managing-conflicts.md]', '[recommended-configurations.md]') instead of inlining all of that content.

Move the marketplace tables, recommended extension stacks, and performance sections into their corresponding reference files to enable one-level-deep progressive disclosure.

DimensionReasoningScore

Conciseness

Dense, mostly lean body using tables and copy-paste commands that assumes Claude's competence; the one explanatory sentence about Microsoft marketplace terms is a relevant niche fact rather than generic concept padding.

3 / 3

Actionability

Provides fully executable guidance throughout — `cursor --install-extension dbaeumer.vscode-eslint`, concrete VSIX download steps, keybindings.json and settings.json blocks, and specific extension IDs — copy-paste ready.

3 / 3

Workflow Clarity

Multi-step processes are sequenced (VSIX install steps 1-5, performance measurement) but lack validation checkpoints; the batch reinstall loop `while read ext; do cursor --install-extension "$ext"; done` has no verification, capping workflow clarity at 2 per the batch-operation guideline.

2 / 3

Progressive Disclosure

Eight bundle files exist in references/ (installing-extensions.md, managing-conflicts.md, performance-optimization.md, recommended-configurations.md, etc.) but the ~215-line body links to none of them, leaving a monolithic wall of text that ignores the available bundle structure.

1 / 3

Total

9

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive: it names concrete capabilities and provides an explicit, natural-language trigger list scoped to Cursor. It does not pad with fluff and is clearly distinguishable from generic VS Code skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions/topics — "Open VSX registry, VSIX installation, conflict resolution, and essential extensions" — comparable to the score-3 example naming several specific actions.

3 / 3

Completeness

Answers both what ("Integrate VS Code extensions with Cursor IDE: ...") and when via an explicit "Triggers on ..." clause, matching the score-3 anchor.

3 / 3

Trigger Term Quality

Explicit trigger list covers natural phrasings a user would say ("cursor extensions", "cursor plugins", "cursor marketplace") plus relevant technical terms ("open vsx", "vsix install").

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Cursor IDE extension integration) with distinct, Cursor-specific triggers, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.