01
Create local skill folders
Build SKILL.md with valid frontmatter and add only the scripts, references, assets, and UI metadata needed by the workflow.
local Codex skill management
CategoryAI & Codex Skills
Codex Local Skills
Codex Local Skills help you create, install, organize, test, update, and troubleshoot reusable workflows that Codex discovers from your computer or repository. Download the skills for managing SKILL.md files, scripts, references, assets, invocation rules, and installation scope without turning every project into a shared package.
Local skillsSKILL.mdSkill discoveryTroubleshooting
01
02
03
04
05
06
07
08
09
02
03
04
05
06
07
08
09
task: complete local codex skill management task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffWhy a specialist workflow matters
A useful skill becomes difficult to trust when it is installed in the wrong scope, has a vague trigger, hides dependencies, or silently conflicts with another skill name.
Codex discovers skills from repository, user, admin, and system locations, then loads the full instructions only when a skill is selected.
These skills help you choose the correct local scope, build valid folders, keep descriptions concise, test explicit and implicit activation, and diagnose discovery or dependency problems.
What the downloadable skills can do
What Codex Local Skills can help accomplish
02
Choose an installation scope
Place skills at repository, parent-folder, user, or managed scope according to who needs them and where they should activate.
03
Test discovery and triggering
Check selectors, explicit invocation, implicit description matching, path visibility, duplicate names, dependencies, and restart behavior.
04
Maintain a local collection
Version skills, review changes, disable or replace workflows safely, avoid secret storage, and prepare selected skills for broader distribution.
A repeatable working process
How the local codex skill management workflow moves from request to verified result
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
workflow.statusREADY
Context → Plan → Work → Verify
01
Define the reusable job
State the trigger, intended users, required inputs, workflow, output, boundaries, and evidence that the skill worked.
02
Build the smallest complete folder
Write focused instructions and add resources only when they reduce repeated context or make fragile steps dependable.
03
Install at the correct scope
Use repository scope for shared project behavior and user scope for workflows that should be available across projects.
04
Test from realistic prompts
Verify discovery, explicit and implicit activation, tool access, outputs, failure handling, and behavior after updates.
Useful across real projects
Where Codex Local Skills fit
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Repository skills
Check in workflows relevant to a project, service, module, framework, quality process, or team convention.
User-level skills
Keep personal workflows available across repositories without adding them to every project.
Skill development
Author, validate, test, revise, and compare a local skill before sharing it with others.
Managed environments
Understand admin and system skills, dependencies, enablement, conflicts, and organization-controlled defaults.
Common requests
Tasks these skills can handle
Start with one defined outcome and provide the source material, constraints, and checks that matter.
01Create a local Codex skill
02Install a skill at user scope
03Add a project skill
04Fix a skill Codex cannot find
05Improve a trigger description
06Add scripts and references
07Test explicit and implicit invocation
08Prepare a local skill for distribution
Who benefits most
Who Is This For?
These skills are designed for people who need dependable local codex skill management work with a visible process.
Codex users
Build reusable workflows for personal tasks and recurring project work.
Development teams
Store shared skills with repositories and keep project-specific context close to the code.
Skill authors
Test discovery, triggering, dependencies, outputs, and updates before distributing a workflow.
Administrators
Understand how managed skills interact with repository and user-level installations.
Good to know:
These skills manage local workflow files. They do not bypass workspace policy, grant tool permissions, install untrusted code without review, or make a local skill automatically suitable for public distribution.
Set up the workflow
Installation Guide
Install the complete skill folder and add the project-specific context before beginning.
Download and extract the local-skills workflow
Keep SKILL.md with authoring, scope, discovery, testing, maintenance, and troubleshooting guidance.
Choose repository or user scope
Use `.agents/skills` in the appropriate repository path, or the supported user-level skills folder for cross-project use.
Review bundled files before activation
Inspect scripts, references, assets, commands, dependencies, network behavior, and any requested credentials.
Test in a fresh task
Confirm the skill appears, triggers on representative prompts, stays inactive on near misses, and produces the intended result.
Before you download
Frequently Asked Questions
Practical answers about capabilities, limits, setup, and review.
Where does Codex load local skills?+
Codex supports repository, user, admin, and system locations. The correct path depends on who should receive the skill and where it should activate.
What is required inside a skill?+
A skill folder needs SKILL.md with valid name and description frontmatter. Scripts, references, assets, and UI metadata are optional.
Why is my skill not appearing?+
Check the folder path, frontmatter, duplicate names, disabled configuration, discovery scope, and whether Codex needs a refresh or restart.
Should I install every skill globally?+
No. Use user scope only for workflows useful across projects. Keep project-specific behavior with the relevant repository or subfolder.
Can a local skill contain secrets?+
It should not. Store credentials in approved environment or connector systems and document only how the skill accesses them.
Make the work repeatable
Give Codex a local skill workflow built around the right scope, clear triggers, reviewed resources, and realistic activation tests.
Clear context. Purposeful work. Relevant checks. A result others can understand.