Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
When invoking the built-in /create-skill command in Cursor while connected to WSL, the command fails with a file not found error. The error shows that Cursor is attempting to access the skill template file using Windows-style backslashes () instead of Unix-style forward slashes (/), causing the path resolution to fail.
Steps to Reproduce
Open Cursor on Windows
Connect to WSL workspace (using WSL remote connection)
Verify skill template exists at ~/.cursor/skills-cursor/create-skill/SKILL.md in WSL
In Agent chat, invoke the /create-skill command
Observe the error
Expected Behavior
The /create-skill command should successfully read the template file from the WSL file system using proper Unix path format:
/home//.cursor/skills-cursor/create-skill/SKILL.md
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.4.0-pre.29.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: 31ba4eea39481b2e13065083d98cf92613175e00
Date: 2026-01-13T20:27:33.722Z
Build Type: Stable
Release Track: Nightly
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100
Additional Information
Actual Behavior
The command fails with the following error:
Error: Unable to read file ‘\home<username>.cursor\skills-cursor\create-skill\SKILL.md’
(Error: Unable to resolve nonexistent file ‘\home<username>.cursor\skills-cursor\create-skill\SKILL.md’)
Note the incorrect use of Windows backslashes () instead of Unix forward slashes (/).
Error Stack Trace
Request ID: cc99ee44-8fdb-4809-80d8-10361a64742e
Error: Unable to read file ‘\home<username>.cursor\skills-cursor\create-skill\SKILL.md’ (Error: Unable to resolve nonexistent file ‘\home<username>.cursor\skills-cursor\create-skill\SKILL.md’)
at $Vc.restoreReadError (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:37044:93581)
at $Vc.doReadFileStream (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:37044:93357)
at async $Vc.doReadFile (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:37044:92598)
at async rW.readFile (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:653:23765)
at async vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35283:2345
at async Promise.all (index 0)
at async CLc._gatherCursorRules (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35283:2154)
Root Cause
The built-in /create-skill command appears to have hardcoded or improperly converted path separators. When running in a WSL context, the command should use Unix-style paths, but it’s using Windows-style backslashes instead.
Does this stop you from using Cursor
No - Cursor works, but with this issue