Incorrect skill name resolution in Automations for nested `.cursor` skills

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Skills nested in folders under .cursor work correctly in the Cursor IDE, but not in Automations.
When skills are placed in subfolders (e.g., .cursor/category/my-skill/SKILL.md), they are incorrectly displayed in Automations as category instead of my-skill.

Steps to Reproduce

Create a skill in a .cursor/category/my-skill/SKILL.md.
Type / in Cursor IDE: it works.
Type / in Cursor Automations (web): it does display category instead of my-skill

Expected Behavior

Cursor Automations display the correct list of nested skills.

Operating System

MacOS

Version Information

Cursor Automations on the Web on March 16, 2026

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This is a known issue. Nested directories under .cursor/skills/ resolve correctly in the IDE, but not in Automations, and not in the CLI.

A similar bug for commands in the CLI was already reported here: Subfolders within Cursor commands folder supported in IDE but not CLI

The team is aware, but there’s no ETA yet. As a workaround, you can move skills up one level of nesting, for example .cursor/skills/my-skill/SKILL.md with no intermediate folders. I know that’s not ideal if the structure matters, but for now it’s the only way to make sure Automations pick them up.

Let me know if you have any questions.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.