Skill Manager scans ~/.codex/skills for Codex-specific global skills and ~/.agents/skills for shared global skills. Each immediate child folder containing a SKILL.md becomes an inventory record. The current release focuses on global user roots, so project-level skill folders require separate inspection.
The two Codex-related roots
| Path | Role in Skill Manager | Typical use |
|---|---|---|
~/.codex/skills | Codex global root | Skills intended for the user's Codex setup |
~/.agents/skills | Shared global root | Skills installed for use across compatible agents |
| Project skill folders | Current release scope excludes these paths | Repository-specific instructions and workflows |
A missing root is a valid state. It can mean that you use a shared root, that an installer chose a different location, or that no global skills have been installed for that agent.
List the detected paths
$ npx github:Ryan-yang125/skill-manager auditThe report should preserve four related fields: root path, full skill path, path relative to the root, and agent classification. Together they tell you where the skill lives and which inventory bucket owns it.
Trace package and source metadata
Folder location shows scope. Package metadata adds provenance. Skill Manager reads installed package information when available and falls back to local grouping when a manifest is missing. Useful fields include the source name, source URL, plugin name, install time, update time, and whether the metadata was inferred.
Inferred metadata deserves a quick review before cleanup. Open the skill content, inspect nearby files, and compare the source repository with the version on disk.
Recognize duplicate locations
The same skill name can appear in shared and Codex-specific roots. That can be intentional when each copy targets a different agent version. It can also indicate a stale install left behind by an older package manager.
- Compare full paths and source URLs.
- Read both
SKILL.mdfiles. - Check modification dates and local usage evidence.
- Choose a canonical copy with a clear update route.
- Archive the confirmed duplicate through a recoverable ledger.
Inspect with standard shell tools
$ find ~/.codex/skills ~/.agents/skills -name SKILL.md -print 2>/dev/nullThe shell result is useful for a quick existence check. Skill Manager adds source grouping, evidence, context estimates, archive history, and exportable reports.
Codex path FAQ
Where does Skill Manager look for Codex skills?
The current release scans ~/.codex/skills and the shared ~/.agents/skills root.
Does Skill Manager scan project-level skills?
The current release focuses on global user roots. Inspect repository-specific skill folders from the project itself.
Why can the same skill appear twice?
A package can install copies into multiple roots, or a shared skill can coexist with an agent-specific copy. Compare path, source, content, and usage before choosing a canonical copy.
Map every global root
Run a local audit and keep exact paths, provenance, and evidence in one report.
Run Skill Manager