coco-research/update-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when the user wants to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
npx skills add https://github.com/coco-research/coco --skill update-cursor-settings
This skill guides you through modifying Cursor/VSCode user settings. Use this when the user wants to change editor settings, preferences, configuration, themes, keybindings, or any settings.json values.
| OS | Path |
|----|------|
| macOS | ~/Library/Application Support/Cursor/User/settings.json |
| Linux | ~/.config/Cursor/User/settings.json |
| Windows | %APPDATA%\Cursor\User\settings.json |
// Read the settings file first
const settingsPath = "~/Library/Application Support/Cursor/User/settings.json";
// Use the Read tool to get current contents
Common setting categories:
editor.fontSize, editor.tabSize, editor.wordWrap, editor.formatOnSaveworkbench.colorTheme, workbench.iconTheme, workbench.sideBar.locationfiles.autoSave, files.exclude, files.associationsterminal.integrated.fontSize, terminal.integrated.shell.*cursor. or aipopup.When modifying settings.json:
| User Request | Setting |
|--------------|---------|
| "bigger/smaller font" | editor.fontSize |
| "change tab size" | editor.tabSize |
| "format on save" | editor.formatOnSave |
| "word wrap" | editor.wordWrap |
| "change theme" | workbench.colorTheme |
| "hide minimap" | editor.minimap.enabled |
| "auto save" | files.autoSave |
| "line numbers" | editor.lineNumbers |
| "bracket matching" | editor.bracketPairColorization.enabled |
| "cursor style" | editor.cursorStyle |
| "smooth scrolling" | editor.smoothScrolling |
// and /* */). When reading, be aware comments may exist. When writing, preserve comments if possible..vscode/settings.json) apply only to the current project.Take coco-research/update-cursor-settings from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.