Summary
Currently, CodexSkillManager only scans user-level skill directories (~/.codex/skills/public and ~/.claude/skills). It would be helpful to also support browsing and managing project-level skills.
Background
Both Claude Code and Codex support project-specific skills stored in:
<project>/.claude/skills/
<project>/.codex/skills/
These are useful for team conventions, project-specific workflows, and skills that should be version-controlled with the codebase.
Proposed Feature
Add the ability to:
- Open/point to a project directory
- Browse skills in that project's
.claude/skills/ or .codex/skills/ folder
- View, edit, and delete project-level skills
- Import skills from Clawdhub directly into a project (not just user-level)
Possible UX
- A "Open Project..." menu option or drag-and-drop support
- Sidebar section for "Project Skills" alongside the existing local skills
- Visual distinction between user-level and project-level skills
Use Case
When working on a team project, I want to manage skills that are specific to that repo without leaving the app or manually copying files.
Thanks for the great app!
Summary
Currently, CodexSkillManager only scans user-level skill directories (
~/.codex/skills/publicand~/.claude/skills). It would be helpful to also support browsing and managing project-level skills.Background
Both Claude Code and Codex support project-specific skills stored in:
<project>/.claude/skills/<project>/.codex/skills/These are useful for team conventions, project-specific workflows, and skills that should be version-controlled with the codebase.
Proposed Feature
Add the ability to:
.claude/skills/or.codex/skills/folderPossible UX
Use Case
When working on a team project, I want to manage skills that are specific to that repo without leaving the app or manually copying files.
Thanks for the great app!