/skills dialog shows 'No skills found' after moving skill files; requires full restart to fix

Description

After moving skill files from .github/skills/ to .claude/skills/, the /skills dialog continued to show "No skills found" even though the skills were correctly loaded and visible in the system-reminder context. Clearing the session (within the same process) did not fix the dialog. Only fully exiting Claude Code and starting a new session resolved it.

Steps to Reproduce

1. Have skills defined in .github/skills/<skill-name>/SKILL.md
2. Move them to .claude/skills/<skill-name>/SKILL.md
3. Open a new conversation (clear session) — skills appear in the system-reminder but /skills dialog shows "No skills found"
4. Fully exit Claude Code and start a new session — /skills dialog correctly shows the skills

Expected Behavior

After a session clear (or at latest, on next conversation start within the same process), the /skills dialog should reflect the same skill list that appears in the system-reminder context.

Actual Behavior

• Skills appear in system-reminder (functionally active and triggerable)
• /skills dialog shows "No skills found" until a full process restart

Environment

• Skills location: .claude/skills/<skill-name>/SKILL.md
• Platform: Linux (devcontainer)
• Claude Code CLI

Additional Context

This suggests the /skills dialog and the system-reminder skill-loading use separate discovery mechanisms or caches that are not synced on session clear — only on full process exit/restart.