[FEATURE] Skill Loading Transparency and Management Commands

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

When using slash commands to invoke skills (e.g., /building-agents), there is currently no indication of where the skill was loaded from when multiple versions exist with the same name. This creates confusion and wasted time debugging why behavior doesn't match expectations.

Proposed Solution

When a skill is invoked, explicitly show the user where it was loaded from, especially when conflicts exist:

✓ Loaded skill: building-agents
  Source: ~/.claude/skills/building-agents/SKILL.md (global)
  ⚠ Note: Workspace also has .claude/skills/building-agents/SKILL.md

  Use '/skill-info building-agents' to compare versions

It is particularly problematic when you have a monorepo, and the skill is located like this https://github.com/adenhq/hive/tree/main/core/.claude/skills/building-agents

Alternative Solutions

Add commands for skill introspection and management:

/skill-list or /skills

List all available skills with their sources:

Available skills:
  building-agents
    - ~/.claude/skills/building-agents/ (global) ← active
    - ./.claude/skills/building-agents/ (workspace)
  testing-agent
    - ~/.claude/skills/testing-agent/ (global) ← active
  custom-skill
    - ./.claude/skills/custom-skill/ (workspace) ← active

/skill-info <name>

Show details about a specific skill:

Skill: building-agents
Active source: ~/.claude/skills/building-agents/SKILL.md
Last modified: 2026-01-20 13:05
Size: 919 lines

Conflicts found:
  ./.claude/skills/building-agents/SKILL.md
  Last modified: 2026-01-21 11:30
  Size: 830 lines
  Diff: 89 lines different

Use '/skill-use <name> --source <path>' to specify which version to load

/skill-reload <name> or /skill-refresh

Clear cached skill and reload from disk:

✓ Reloaded skill: building-agents
  Source: ~/.claude/skills/building-agents/SKILL.md

/skill-use <name> --source <local|global|path>

Explicitly choose which version to load:

/skill-use building-agents --source local
✓ Loaded building-agents from ./.claude/skills/building-agents/

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

Scenario that occurred:

1. User had skill at ~/.claude/skills/building-agents/SKILL.md (global, older version)
2. User also had skill at ./hive/.claude/skills/building-agents/SKILL.md (workspace-local, newer version)
3. Ran /building-agents command
4. Claude loaded the global version without any indication
5. Resulted in following completely wrong instructions (old MCP-based approach vs new Python-file-based approach)
6. Wasted significant time before user manually discovered the version mismatch

The command message only showed:

<command-name>/building-agents</command-name>
Base directory for this skill: /home/timothy/.claude/skills/building-agents

But this wasn't visible to the user, and Claude didn't realize there was a conflict.

Additional Context

_No response_