01
Design repository-scoped workflows
Turn recurring project tasks into skills with clear triggers, required context, commands, outputs, boundaries, and verification.
repository-scoped Codex skills
CategoryAI & Codex Skills
Codex Project-Level Skills
Codex Project-Level Skills help teams store reusable workflows inside a repository so Codex can follow the project's architecture, commands, quality checks, formats, and delivery process. Download the skills for creating shared repository guidance that activates only where it belongs.
Project scopeRepository skillsTeam workflowsQuality checks
01
02
03
04
05
06
07
08
09
02
03
04
05
06
07
08
09
task: complete repository-scoped codex skills task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffWhy a specialist workflow matters
A global workflow often becomes too broad, while a prompt repeated in every task is easy to forget and difficult for a team to maintain.
Project-level skills belong near the code and can be scoped from the repository root down to a relevant working folder.
These skills help teams decide where a workflow should live, separate durable repository guidance from task instructions, and build project-specific skills that remain small and testable.
What the downloadable skills can do
What Codex Project-Level Skills can help accomplish
02
Place skills at useful depth
Install root skills for the whole repository or nested skills for a service, package, module, or specialized folder.
03
Connect project evidence
Reference local architecture, schemas, templates, scripts, fixtures, style rules, tests, and release procedures without duplicating them.
04
Review and evolve team skills
Version changes, test activation, avoid overlapping names, document dependencies, and update workflows as the repository changes.
A repeatable working process
How the repository-scoped codex skills 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
Identify repeated project work
Choose a task that benefits from durable steps, local knowledge, specialized tools, or consistent verification.
02
Define scope and ownership
Decide which repository area should see the skill, who maintains it, and what belongs in AGENTS.md instead.
03
Build with project references
Keep SKILL.md focused and link to the repository files, scripts, templates, and checks that provide current context.
04
Test with the team workflow
Run representative tasks from relevant directories, verify activation and output, and review changes through normal repository controls.
Useful across real projects
Where Codex Project-Level Skills fit
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Repository root
Share workflows that apply across the whole codebase, such as review, release, documentation, or architecture checks.
Modules and packages
Scope skills to a library, application, service, mobile module, data pipeline, or infrastructure folder.
Quality workflows
Standardize testing, accessibility, security, migration, documentation, release, and handoff procedures.
Team-specific processes
Encode ticket handling, code generation, incident work, data reviews, or client delivery practices tied to one project.
Common requests
Tasks these skills can handle
Start with one defined outcome and provide the source material, constraints, and checks that matter.
01Create a repository skill
02Choose the correct project location
03Separate AGENTS.md from SKILL.md guidance
04Reference project scripts
05Add acceptance checks
06Test activation from nested folders
07Review a skill change
08Maintain shared skill ownership
Who benefits most
Who Is This For?
These skills are designed for people who need dependable repository-scoped codex skills work with a visible process.
Software teams
Share recurring workflows without requiring every developer to maintain a personal copy.
Repository maintainers
Keep project-specific instructions, references, and verification close to the code they govern.
Platform teams
Provide scoped workflows for services, infrastructure, releases, migrations, and operational checks.
Open-source maintainers
Help contributors and Codex follow project conventions, commands, boundaries, and review expectations.
Good to know:
Project-level skills can guide repository work, but they do not override higher-priority policy, grant access, replace code review, or justify storing credentials and private data in the repository.
Set up the workflow
Installation Guide
Install the complete skill folder and add the project-specific context before beginning.
Download and extract the project-level skills
Keep SKILL.md with scoping, authoring, references, testing, ownership, and maintenance guidance.
Choose the repository location
Place the skill under `.agents/skills` at the root or relevant nested path based on who should receive it.
Connect local project context
Reference AGENTS.md, architecture, commands, templates, schemas, fixtures, tests, and review procedures.
Commit and test the workflow
Review the folder like code, run representative prompts from applicable paths, and verify activation and outputs.
Before you download
Frequently Asked Questions
Practical answers about capabilities, limits, setup, and review.
What makes a skill project-level?+
It is stored with the repository and discovered only when Codex works within the applicable repository path.
Should project rules go in AGENTS.md or a skill?+
Use AGENTS.md for durable conventions that always apply. Use a skill for a reusable workflow selected for matching tasks.
Can a nested folder have its own skill?+
Yes. Nested project locations are useful when a workflow belongs to one service, module, or specialized area.
Will project skills be shared with the team?+
Yes, when the skill folders are committed and team members use a Codex environment that supports repository skill discovery.
How should project skills be updated?+
Review and version them through the same repository process as other important project files, with representative tests after changes.
Make the work repeatable
Give your repository Codex skills that activate in the right project area and carry the exact workflow, references, and checks the team maintains.
Clear context. Purposeful work. Relevant checks. A result others can understand.