Skills not loaded from CLAUDE_CONFIG_DIR — hardcoded to ~/.claude/skills/

Bug Description

When CLAUDE_CONFIG_DIR is set to a custom directory (e.g., C:\Users\User\.claude-custom), Claude Code ignores that directory for skills lookup and always searches for skills in ~/.claude/skills/ (the default path).

Steps to Reproduce

1. Set CLAUDE_CONFIG_DIR to a custom path (e.g., ~/.claude-custom)
2. Create skills in ~/.claude-custom/skills/ (e.g., rest-api-design.md with proper frontmatter)
3. Open Claude Code and run /skills

Expected Behavior

Skills located in $CLAUDE_CONFIG_DIR/skills/ should be loaded and displayed in the /skills dialog, and available as slash commands (e.g., /rest-api-design).

Actual Behavior

The /skills dialog shows "No skills found" with the message:

Create skills in .claude/skills/ or ~/.claude/skills/

Skills in $CLAUDE_CONFIG_DIR/skills/ are completely ignored.

Environment

• Platform: Windows 10 (MSYS/bash)
• Shell: bash (MSYS_NT-10.0-19045)
• CLAUDE_CONFIG_DIR: set to a custom path
• Skill file: valid .md with correct frontmatter (name, description fields)

Context / Use Case

Users with multiple Claude accounts rely on CLAUDE_CONFIG_DIR to keep configurations isolated per account. If skills are always loaded from ~/.claude/skills/, it breaks the isolation — skills intended for one account would bleed into the other.

The expected behavior is that all config artifacts (settings, memory, skills) are resolved relative to CLAUDE_CONFIG_DIR, not hardcoded to ~/.claude/.

Workaround

None currently available without putting skills in ~/.claude/skills/, which defeats the purpose of CLAUDE_CONFIG_DIR.