codex - 💡(How to fix) Fix Support project-scoped personal skill discovery directories

What variant of Codex are you using?

CLI / App

What feature would you like to see?

Codex should support custom, project-scoped personal skill discovery directories.

Today, Codex can discover personal/user skills from locations such as:

~/.agents/skills/<skill-name>/SKILL.md

and team/project skills from project-local locations. [[skills.config]] can configure individual skills, such as disabling a skill by path, but it does not appear to provide a way to add extra skill discovery directories.

The gap is for personal skills that are project-specific but should not be committed to the team repository.

Use case

I may keep personal Codex skills in a private repo, for example:

~/Documents/my_git/my_private_skills/
  better_auth_play/
    review-helper/
      SKILL.md
    implementation-helper/
      SKILL.md
  other_project/
    deploy-helper/
      SKILL.md

Some of these skills are reusable personal workflow helpers, but only for one project. They are not team skills, so I do not want to commit them into the project repository.

Current workarounds

1. Put them in ~/.agents/skills.

   This makes them global, so project-specific personal skills become ambient in every project unless carefully scoped or made manual-only.

2. Symlink them into ~/.agents/skills.

   This keeps the source of truth in a private repo, but still makes the skills globally visible. If I work across multiple projects, I either get global bleed or need a switching script.

3. Symlink them into the team project.

   This is not suitable. A symlink like:

   .agents/skills/my-personal-skill -> /Users/me/private/path

   can work locally, but if committed it is broken for teammates/CI/remotes and leaks local machine paths.

Requested behavior

Support config that lets a project declare local-only personal skill directories outside the repository.

For example:

[projects."/path/to/project".skills]
dirs = [
  "~/Documents/my_git/my_private_skills/better_auth_play",
]

or:

[[skills.dir]]
path = "~/Documents/my_git/my_private_skills/better_auth_play"
scope = "/path/to/project"
enabled = true

Codex would scan each configured directory for:

<skill-name>/SKILL.md

using the same discovery behavior as ~/.agents/skills.

Expected behavior

• Personal project-specific skills can be discovered only when working in the matching project.
• Skills remain outside the team git repo.
• No repo-local symlinks need to be committed.
• No global skill bleed across unrelated projects.
• No manual symlink switching script is required.

Why this matters

The current locations work well for:

• team skills committed to a repo
• truly global personal skills

But they are awkward for:

• private personal skills
• project-specific workflows
• skills stored in a separate private repository
• users working across many projects with different personal automation

This is related to broader skill/profile scoping requests such as #22692 and #17545, but this issue is narrower: it is specifically about adding custom skill discovery directories with project scope.

Additional information

--add-dir helps with filesystem access, but it does not appear to make Codex scan that directory for skills.

[[skills.config]] can configure a specific skill path, but it does not appear to act as a discovery path for a directory of skills.