Agent Skills in Codex, Claude Code and Cursor
Compare project and personal directories, discovery and invocation in three agents. Check remote scope, frontmatter and runtime requirements before reusing a package.
Fastest way
Ask your AI to do it
Paste this into the AI agent you already use:
Help me use a Skill with another agent. Ask which agents and package I use, check supported locations and tools, identify any assumptions to change, and verify the workflow with a small example.
Portable files still need a host check
The SKILL.md format can travel between supported hosts; discovery, invocation and execution are separate checks. Keep the package intact and inspect agent-specific instructions before reuse. Skillrove host labels describe installation targets, not a certification that every workflow ran in every client.
Codex: repository scope and CLI or IDE selection
Use .agents/skills/SKILL_SLUG in the repository or ~/.agents/skills/SKILL_SLUG personally. Codex CLI and IDE support /skills and $ selection. ChatGPT uses a distinct @ selector in the official guide; check the surface you opened.
Codex locations and CLI/IDE invocation
Claude Code: project folders and /name
Use .claude/skills/SKILL_SLUG or ~/.claude/skills/SKILL_SLUG and invoke a user-invocable skill with /name. Review user-invocable, disable-model-invocation, context: fork and dynamic ! commands; those fields do not guarantee equivalent behavior in another host.
Claude Code locations and /name invocation
Cursor: discovery UI and personal Cloud sync
Project locations include .cursor/skills and .agents/skills; personal locations include ~/.cursor/skills and ~/.agents/skills. Check Customize → Skills and select with / in Agent chat. Only ~/.cursor/skills participates in opted-in personal Cloud sync; the other personal folder and unsynced files stay local.
Cursor discovery and Cloud scope
Verify an example in the target environment
Confirm the package’s name and scope, read its tool and runtime requirements, then run its documented practice input into a fresh folder. Inspect exported files, calculations or unchanged tests as appropriate. A preview, a successful download and a discovered name each establish a different stage.
Compare runtime and actual deliverables
Locate the first failing stage
Keep package, model and service access separate
Skillrove access unlocks a package under its download rules. It does not supply a model subscription, provider credit, remote filesystem, browser tool or external credentials. Confirm the requirements for the workflow you selected.