AGENT SKILLS
Codex Skills Setup and Project Scope
Use a local skill for a repeatable task in your own workspace, and a plugin when you need to distribute a bundle. Current Codex discovery centers on .agents/skills, so older install paths need care.
On this page
CodexLocate, invoke and share Codex skills
01Codex discovers repository and personal skills in different locations.
02A task can trigger a skill implicitly or through an explicit mention.
03Local installation and reusable plugin distribution are separate routes.
Start with one practical task
Pick one project task and check where the client loads the skill. Confirm that the task description triggers the intended workflow, then record the files, dependencies and output another contributor will need.
Use current local scope
Current docs list .agents/skills in the repository hierarchy and ~/.agents/skills for personal local skills. Name and description drive discovery; scripts and assets are optional.
Invoke deliberately and keep descriptions focused
Codex can match a task implicitly or accept an explicit skill mention. A useful description states when the workflow applies. For UI work, choose design guidance; for repeated repository work, define a narrow repeatable task.
Choose local install or distribution
The official guide uses skill-installer for curated local setup and other repositories. For reusable distribution or bundles with connectors, it directs authors to plugins. Check the current surface before copying older install commands.
A few more details
Must every skill contain scripts?
No. An instruction-only SKILL.md can define a useful workflow.
Why does a skill not appear?
Check scope, folder structure and metadata. The official guide advises restarting if a newly detected change does not appear.
Sources & maker notes
This guide is based on the cited documentation and maker sources. vibeforthat has not run an independent installation or end-to-end product test for this article.