Skip to main content
A skill packages instructions for a focused task in a folder containing SKILL.md. It can include scripts, templates, and reference files. Providers discover skills differently. Mains exposes a skill picker for Claude and Codex, while Copilot can load its configured skill directories without that picker.

​
Locations

A Codex installation can use agent skill directories such as .agents/skills/ and existing Codex-specific locations. Discovery follows the installed runtime; see the official skills guide.

​
Create a project skill

For Claude, create .claude/skills/review-changes/SKILL.md:
Use a specific description so the agent can match it to a task. Add supporting files only when they help the workflow. Provider-specific frontmatter controls can differ. Check the provider’s documentation before relying on a permission or invocation field.

​
Invoke a skill

Use the composer’s command or mention menu to select an available skill. Claude can also invoke matching skills automatically. Click a skill chip to open its file or plugin detail. If a new skill does not appear, refresh provider capabilities or start a new session after installation.

​
Install a shared skill

Use the publisher’s installation instructions. The community skills CLI can install skills for a selected agent:
Check the CLI’s selected agent, scope, and destination before accepting. An install command does not always put the skill in the same directory for every provider.

​
Skills and access

A skill provides instructions; it does not independently grant filesystem access or connect an account. The run’s mode, permissions, and tool availability still apply.