claude-code - 💡(How to fix) Fix [Feature Request] Support project-scoped local skills (`.claude/skills.local/` or `local: true` frontmatter) [1 comments, 2 participants]

TL;DR

Support for a project-scoped, non-shared skills directory, such as .claude/skills.local/, is likely the most straightforward fix.

Guidance

• Consider adding a .claude/skills.local/ directory that is auto-gitignored, similar to settings.local.json, to store project-specific skills that should not be shared with the team.
• Evaluate the feasibility of introducing a local: true field in the SKILL.md frontmatter to opt-out of sharing specific skills.
• Assess the trade-offs between using .git/info/exclude with a naming convention like local-* versus implementing a more explicit solution like .claude/skills.local/.
• Review the current implementation of scope handling for skills to determine the best approach for integrating the proposed solution.

Example

No code snippet is provided as the issue focuses on proposing a new feature rather than fixing a specific code issue.

Notes

The proposed solutions aim to address the lack of a documented equivalent to settings.local.json or CLAUDE.local.md for personal, project-scoped skills. However, the implementation details and potential interactions with existing features are not fully explored in the issue.

Recommendation

Apply a workaround, such as using .git/info/exclude with a naming convention like local-*, until a more explicit solution like .claude/skills.local/ or a local: true field in SKILL.md frontmatter is implemented, as it provides a functional, albeit undocumented, way to manage project-specific skills without sharing them with the team.