cursor-extension-integration
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-extension-integrationManage integrate VS Code extensions with Cursor. Triggers on "cursor extensions", "cursor vscode extensions", "cursor plugins", "cursor marketplace". Use when working with cursor extension integration functionality. Trigger with phrases like "cursor extension integration", "cursor integration", "cursor".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
35%This skill provides a basic structural outline for Cursor extension integration but lacks the concrete, actionable guidance needed for effective use. The instructions are too generic (e.g., 'configure extension settings' without specifying which settings or how), and critical details are deferred to external files without providing sufficient standalone value. The skill would benefit significantly from specific extension recommendations, actual configuration examples, and concrete conflict resolution steps.
Suggestions
Add specific extension names and concrete configuration examples (e.g., 'To disable Copilot: Settings > Extensions > GitHub Copilot > Disable')
Include actual keybinding conflict examples and resolution commands (e.g., specific keybindings.json entries)
Provide inline examples of common tasks rather than deferring entirely to external files
Add validation steps: how to verify an extension installed correctly, how to confirm conflicts are resolved
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary framing ('This skill helps...', 'Overview' section restating the obvious). The prerequisites section explains things Claude would know (what VS Code marketplace access means). | 2 / 3 |
Actionability | Instructions are vague and lack concrete guidance - 'Check compatibility and conflict warnings' and 'Configure extension settings' provide no specific commands, code, or examples. No actual extension names, settings paths, or executable steps are given. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. No guidance on how to verify successful installation, how to identify conflicts, or what to do if something fails. The 'disable conflicting AI extensions' step is buried without explanation of why or how to identify conflicts. | 2 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present but use placeholder syntax '{baseDir}' which isn't actionable. The main content is appropriately brief but delegates too much to external files without providing enough standalone value. | 2 / 3 |
Total | 7 / 12 Passed |
Activation
40%This description suffers from vague language, a grammatical error ('Manage integrate'), and circular reasoning in its 'when' clause. While it attempts to include trigger terms, the inclusion of 'cursor' alone as a trigger is problematic, and the description fails to specify what concrete actions the skill actually performs with VS Code extensions.
Suggestions
Fix grammar and list specific actions: 'Install, configure, and sync VS Code extensions with Cursor. Manage extension compatibility and marketplace integration.'
Replace the circular 'when' clause with concrete scenarios: 'Use when installing VS Code extensions in Cursor, syncing extensions between editors, or troubleshooting extension compatibility.'
Remove overly generic trigger 'cursor' and add more specific natural phrases like 'install extension in cursor', 'cursor extension compatibility', 'sync vscode extensions to cursor'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage integrate' (grammatically incorrect) and 'working with cursor extension integration functionality' without listing concrete actions. No specific capabilities like 'install', 'configure', 'sync', or 'troubleshoot' are mentioned. | 1 / 3 |
Completeness | Has a weak 'what' (manage/integrate extensions) and includes trigger phrases, but the 'when' clause is circular ('Use when working with cursor extension integration functionality') rather than describing actual user scenarios or needs. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'cursor extensions', 'cursor vscode extensions', 'cursor plugins', 'cursor marketplace', but the final trigger 'cursor' alone is far too generic and would cause false positives. Missing natural phrases like 'install extension in cursor' or 'add plugin to cursor'. | 2 / 3 |
Distinctiveness Conflict Risk | The trigger term 'cursor' alone would conflict with any cursor-related skill. While 'cursor extensions' and 'cursor marketplace' are more specific, the overly broad triggers reduce distinctiveness. | 2 / 3 |
Total | 7 / 12 Passed |
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.