[FEATURE] Add option to configure skills path

Resolved 💬 5 comments Opened Jan 16, 2026 by dimonchik0036 Closed Mar 1, 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

Currently, Claude Code only discovers skills from fixed paths:

  • ~/.claude/skills/ (personal)
  • .claude/skills/ (project)

Some projects prefer to organize AI-related configuration files in a dedicated directory like .ai/ rather than .claude/. This keeps all AI tooling configuration (prompts, skills, guidelines) in one consistent location without dependency on a particular agent

Proposed Solution

Allow users to configure custom skill discovery paths via settings.json or .claude/settings.json:

  {
    "skills": {
      "additionalPaths": [".ai/skills"]
    }
  }

Or at the project level in .claude/settings.json:

  {
    "skillPaths": [".ai/skills", "tools/claude-skills"]
  }

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

Consistent project structure — Projects using .ai/ for AI-related configs (guidelines, prompts) want skills in the same location (considering https://agentskills.io/specification)

Additional Context

Current Workaround

Using symlinks (ln -s ../.ai/skills .claude/skills) works but adds friction and can cause issues with some version control workflows

View original on GitHub ↗

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