[FEATURE] Custom skills directory paths via env var or settings

Resolved 💬 3 comments Opened Feb 3, 2026 by JayDoubleu Closed Feb 3, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Skills can only be loaded from hardcoded paths:

  • ~/.claude/skills/
  • <project>/.claude/skills/
  • Plugin-relative paths

No way to point Claude at a custom directory like .agents/skills/ without symlinks or complex plugin setups.

Use Cases

  • Project uses .agents/skills/ or scripts/claude/skills/ for organization
  • Don't want to restructure repo or maintain symlinks
  • Want team to share skills from a custom location

Potential Solutions

Option A: Environment variable

CLAUDE_SKILLS_PATH=".agents/skills"

Option B: Settings.json

{
  "additionalSkillsPaths": [".agents/skills"]
}

Option C: Support ${CLAUDE_PROJECT_DIR} in plugin.json skills paths
Currently only ${CLAUDE_PLUGIN_ROOT} works.

Priority

Medium - Quality of life

---

This issue was created using Claude Code 🤖

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗