Slash command switching Skill lag

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Now it feels a bit laggy after using the slash command.

Steps to Reproduce

In the Agent dialog, enter / and switch skills up and down

Operating System

MacOS

Version Information

Version: 2.5.24 (Universal)
VSCode Version: 1.105.1
Commit: 77bf005db89a809d9c79f4adcb9c9b1b56165390
Date: 2026-02-23T22:03:40.062Z
Build Type: Stable
Release Track: Early Access
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin x64 22.4.0

Additional Information

I suspect it’s because the full preview of all skill content is provided. There’s no need to preview the entire content of each skill; a summary preview should suffice.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. Your hypothesis makes sense. If the preview during navigation renders the full content of each skill, that could definitely cause noticeable lag, especially with long skills.

A couple of questions so we can dig deeper:

  1. How many skills do you have set up? Are any of them especially large with a lot of content?
  2. Can you record a short screen video that shows the lag? That’ll help the team gauge how serious the issue is.

There is usually / only slight lag when activating for the first time or switching before a skill.

Not many, no more than 10 skills, and I also noticed an issue: are the skills listed here only at the project level? Will global skills not be listed here? However, entering “/keyword” allows you to find global skills.

Thanks for the details and the screenshot.

About the lag, it does sound like rendering the full skill preview on every navigation step could be causing it. I’ve flagged this to the team. I don’t have a timeline for a fix yet, but your report helps us prioritize it.

On your second point about global skills not showing up in the / list, good catch. Global skills (from ~/.cursor/skills/) should appear there along with project-level ones. If they’re searchable via /keyword but don’t show up in the initial list, that does look like a bug. I’ll flag this separately too.

Let me know if you run into anything else.