Feature Request: Configurable skills search paths & TUI settings management #11189

Feature Request

Summary: Add JSON config and TUI-based management for skills search directories

Current Situation

Version: 1.1.42

The symlink workaround works:

New-Item -ItemType SymbolicLink -Path ~/.config/opencode/skills -Target ~/.claude/skills

After which opencode debug skill shows skills from both locations. However, this is not well-documented and requires manual CLI setup.

Problem

1. No JSON configuration - Skills search paths are hardcoded in source, not configurable via opencode.json
2. No TUI settings management - Cannot toggle directories or change search priority through the interface
3. Documentation gap - Not clear how to share skills between Claude Code and OpenCode

Proposed Solution

Part 1: JSON Configuration

Add skills section to opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "skills": {
    "search_paths": [
      "C:\Users\<user>\.claude\skills",
      "C:\Users\<user>\.config\opencode\skills",
      ".opencode/skills/"
    ],
    "enabled": true
  }
}

Part 2: TUI Settings Management

Add a settings UI (maybe accessible via Ctrl+S or a settings command) that allows:

• Toggle directories on/off for skill searching
• Reorder search priority via drag-and-drop or arrow keys
• Add custom paths through the UI
• Visual indicator of which directory each skill loaded from

Example TUI flow:

┌─ OpenCode Settings ─────────────────┐
│ Skills Search Paths:                │
│ ☑ C:\Users\...\.claude\skills      │
│ ☑ C:\Users\...\.config\opencode\   │
│ ☑ .opencode/skills/                │
│                                    │
│ [↑↓] Reorder  [Enter] Toggle       │
│ [+ ] Add custom path               │
│ [Esc] Save & Exit                  │
└────────────────────────────────────┘

Use Cases

1. Share skills between Claude Code and OpenCode without symlinks
2. Disable project-specific skills temporarily when working on shared projects
3. Prioritize global skills over local ones (or vice versa)
4. Add team skill libraries from network shares or cloud storage

Alternatives Considered

• Symlink workaround - Works but not discoverable, requires CLI
• Environment variables - Already supported via OPENCODE_CONFIG_DIR, but single path only and no UI

References

• Claude Code has configurable search_paths for skills
• Users increasingly use multiple AI CLI tools and want to share configuration