Get started

Install Duaer skills in Cursor, Claude Code, and Codex

Put a Duaer skill in a folder your agent scans, check that it is listed, then call it by name. The same SKILL.md works in Cursor, Claude Code, and Codex.

Where each agent looks

Cursor: .cursor/skills/ or .agents/skills/ in the project; ~/.cursor/skills/ or ~/.agents/skills/ for all projects. Cursor also reads .claude/skills/ and .codex/skills/.
Claude Code: .claude/skills/ in the project, from the folder you start in up to the repository root; ~/.claude/skills/ for all projects.
Codex: .agents/skills/ from the current folder up to the repository root; ~/.agents/skills/ for all projects.

Use one folder per skill. The folder name matches the skill name, and the file is SKILL.md. To serve all three agents from one repository, keep the real folder in .agents/skills/ (read by Cursor and Codex) and a copy in .claude/skills/ (for Claude Code).

Install a Duaer skill

Pick a skill on skills.duaer.com, or select Copy skill in the Duaer data market.
Create a folder named after the skill, such as duaer-weather.
Save the skill as SKILL.md in that folder. The first line must be ---. Pages on skills.duaer.com start with an index line, so drop everything above the first ---. The commands below do this for you.
Start a new chat, or restart the CLI, so the agent scans again.

mkdir -p .agents/skills/duaer-weather
curl -s https://skills.duaer.com/weather.md | sed -n '/^---$/,$p' > .agents/skills/duaer-weather/SKILL.md
mkdir -p .claude/skills
cp -R .agents/skills/duaer-weather .claude/skills/

For another skill, replace weather with its address on skills.duaer.com and duaer-weather with its name.

Check that the agent can see it

Cursor editor: type / in Agent chat and search for the skill, or open Customize → Skills.
Cursor CLI: type / in the CLI and search again. Users report folders that the editor loads and the CLI does not, so check both if you use both.
Claude Code: run /skills, or ask "What skills are available?".
Codex: run /skills, or type $ and look for the name.

If the skill is missing, check the folder name, the name line in SKILL.md, and that --- is the first line.

Use real folders, not symlinks

Claude Code and Codex follow symlinked skill folders, but users report symlinked skills that run yet do not appear in the / menu, or that load in one app and not in another. A copied folder behaves the same everywhere. To keep one source, copy it in with a script instead of linking it.

Call a skill that does not start on its own

Agents pick a skill by its description. If it does not start on its own, name it: /duaer-weather in Cursor or Claude Code, $duaer-weather in Codex.
With many skills installed, agents shorten or drop some descriptions, and matching gets worse. Move out skills you do not use.

Move skills to another machine or teammate

Commit project skills (.agents/skills/, .claude/skills/) to the repository. Anyone who clones it gets them.
User-level skills (folders under ~/) stay on one machine. Copy the folders, or run the install commands again.
Cursor Cloud Agents get ~/.cursor/skills/ only after you turn on Sync Skills for Cloud Agents. Claude Code cloud sessions read skills committed to the repository, not ~/.claude/skills/ on your machine.

Questions

Does a Duaer skill need a separate file for each agent?

No. A Duaer skill is one SKILL.md. Put the same folder where each agent looks.

Why drop the first line of a skills.duaer.com page?

Duaer skill pages on skills.duaer.com start with an index line for readers. Agents read the skill header only when --- is the first line, so a Duaer skill saved as-is may not start on its own.

Does installing a Duaer skill use credits?

No. Duaer charges only when a data skill runs a search that returns rows.

In this section