Codex Skill Appear as Rules

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I recently started using the Codex desktop app (MacOS) and created a few skills from there to test it out. When I was examining the Cursor settings, I see that they show up as rules and not skills.

Steps to Reproduce

  • On MacOS, create a skill or add existing ones via the Codex desktop app.
  • Verify that the skill exists in ~/.codex/skills
  • In the Cursor Settings, toggle Include third-party Plugins, Skills, and other configs
  • You’ll see they appear as Rules, rather than skills.

Expected Behavior

I expect it to appear as skills, not rules, and be able to access them via the standard / way; not applied as rules.

Screenshots / Screen Recordings

cursor-toggle-enabled.png
cursor-toggle-enabled.png682×609 45.5 KB

cursor-toggle-disabled
cursor-toggle-disabled682×419 29.2 KB

cursor-codex-dir
cursor-codex-dir670×391 59 KB

Operating System

MacOS

Version Information

Version: 2.5.20 (Universal)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Here’s the cursor directory for good measure.

cursor-cursor-dir
cursor-cursor-dir639×443 30 KB

When searching for this issue, I found this one which is somewhat related, but not directly related to codex: Skills are installed as Rules

Maybe the codex app is installing it via a similar way or something.

5

Hey, this is a known issue. Skills installed via third-party tools (Codex desktop, npx skills add, etc.) are currently being classified as Rules instead of showing up under Skills in Cursor settings. A few users have reported the same thing recently:

The ~/.codex/skills/ path is supported as a skills directory per the docs, so your setup looks correct.

Can you share the contents of one of the SKILL.md files from ~/.codex/skills/? I’m especially interested in the frontmatter at the top. That’ll help confirm whether the metadata is being parsed correctly or if Cursor is misclassifying them either way.

The team is aware. No ETA yet, but your report (and the others) helps us prioritize it.

6

Thanks for the update. Not a high priority item for me, fwiw.

Here’s one from a Codex skill marketplace installation (~/.codex/skills/figma/SKILL.md).

---
name: figma
description: Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
---

# Figma MCP

For comparison, here’s the skill-builder one that comes with cursor.

---
name: create-skill
description: Guides users through creating effective Agent Skills for Cursor. Use when you want to create, write, or author a new skill, or asks about skill structure, best practices, or SKILL.md format.
---
# Creating Skills in Cursor

Both looks pretty standard to me with whitespacing, etc.

7

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