Cmd. /skills
Browse and apply local skills for task-specific behavior.
Key takeaways
- Browse and apply local skills for task-specific behavior.
- Check the input surface and availability before using the examples below.
Purpose
Browse and apply local skills for task-specific behavior.
/skillsAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | — |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
The installed command menu and account or organization settings determine availability.
Examples
/skillsWhen to use it
- Select the Figma skill to pull design context and screenshots from an exact node before implementation.
- Use
$imagegenfor UI mock directions or$playwrightto verify the implementation in a real browser. - Confirm that team-provided skills are visible in the current session.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/skills | Applies task-specific instructions | A workflow has a reusable skill |
/plugins | Manages bundled capabilities | You need plugin inventory or marketplace controls |
/apps | Inserts app connectors | You need external app context |
Effects and persistence
Shows available skills. Executing a skill or changing its visibility is a separate action from opening the list.
/skills lets you browse available Codex skills and apply the relevant skill context to a task.
Cautions
- Skills can load from project, user, or administrator locations.
- Skills that depend on scripts or MCP servers need the same approval policy review as other tools.
- Figma, ImageGen, and Playwright are not built-in
/designcommands. Use the exact token exposed by the/skillspicker and installed bundle.
Official sources
Complete command list · Verification scope · History for this command