Skills
See the skills your agents can use in each project, and where they come from.
What a skill is
A skill is a Markdown file, usually a SKILL.md in a folder of its own, with a name, a description of when to use it, and instructions for the agent. Plugins can bring skills too, and some agents ship with skills of their own.
Each agent finds and runs its own skills. OpenOrc lists the skills each agent can use in a project and helps you call one from the composer. It doesn't install or change skills.
Browse skills
- Click Settings at the bottom of the sidebar, then Skills.
- Choose a project in Project. Project skills differ from one project to the next.
- Choose one of your enabled agents. Each button shows how many skills that agent has in the project.
- Type in Search skills to filter by name, description, or path. Click a skill to see its Location.
The list groups skills by where they come from:
| Group | What it holds |
|---|---|
| Project skills | Skills in the project's own skill folders |
| Your skills | Skills in your home folder, available in every project |
| Plugin skills | Skills from plugins you installed |
| Built-in skills | Skills that come with the agent |
Click Refresh skills after you add or remove a skill. The Project menu lists the projects you've added to OpenOrc. Workspace conversations have their own list, described below.
Where skills come from
Each agent has its own skill folders and its own rule for which skill wins when two share a name. OpenOrc applies the same rules, so the list shows the skill the agent would pick.
| Agent | How OpenOrc finds its skills |
|---|---|
| Codex | Asks Codex for its list in the project folder. The list includes Codex's plugin and built-in skills, and only the skills that are turned on. |
| Claude Code | Reads .claude/skills and .claude/commands in the project folder, the same two folders in ~/.claude (or in CLAUDE_CONFIG_DIR), and the skills and commands of plugins installed in Claude Code. Plugin skills are named plugin:skill. When a personal skill and a project skill share a name, the personal one wins, and a skill wins over a command of the same name. Skills bundled with Claude Code itself and skills synced from claude.ai aren't listed. |
| OpenCode | Starts OpenCode for a moment in the project folder and asks it for its skills, built-in ones included. If that fails, OpenOrc reads the folders OpenCode uses, such as .opencode/skills and ~/.config/opencode/skills, and any sources listed under skills in opencode.json. |
| Oh My Pi | Asks omp skill list --json, including its native provider and plugin skill sources. |
| Pi | Asks Pi for its native skill commands in the project. Custom extensions are disabled, as in OpenOrc conversations. |
| Cursor | Reads project and personal .cursor/skills, .agents/skills, and Cursor's Claude/Codex compatibility folders. |
| Antigravity | Reads project .agents/skills and personal .gemini skill folders. Manifest and plugin skills are not enumerated here yet. |
| fx | Reads project .fx/skills, personal $FX_HOME/skills, and the standard compatibility folders fx uses. |
Use a skill in a conversation
The composer suggests the skills of the conversation's current agent, with the project's own first. Scroll the list or keep typing to narrow it. How you open it depends on the agent:
- Claude Code, Cursor, and Antigravity: type / and pick a skill. OpenOrc inserts
/name, which the agent resolves using its own skill rules. - Codex and fx: type / or $ and pick a skill. OpenOrc inserts
$name, the form those agents use. - Pi and Oh My Pi: choose a skill from the composer to insert
/skill:name. - OpenCode: there's no picker. Ask it to use a skill by name, and it loads the skill with its own skill tool.
The suggestions refresh every minute, so a skill you install while a conversation is open shows up without restarting anything.
A Workspace conversation works in a folder you choose, so its picker lists that folder's project skills, along with your personal and plugin skills.
Next steps
Checked against OpenOrc's source on November 9, 2026.