Skills created mid-session not available in slash-command autocomplete until session restart

Description

When a new skill is created at ~/.claude/skills/*/SKILL.md during an active Claude Code session (either in the CLI or via the Cursor/VS Code extension), the skill is registered in the Claude Code runtime's internal skill list but does not appear in the slash-command autocomplete dropdown until the session is restarted.

Steps to reproduce

1. Open a Claude Code session in Cursor
2. Create a new skill: mkdir -p ~/.claude/skills/my-skill && echo "# my-skill\nDoes something." > ~/.claude/skills/my-skill/SKILL.md
3. Type /my-skill in the chat input
4. Expected: The skill appears in the autocomplete dropdown
5. Actual: The skill does not appear. It only appears after closing and reopening the Claude Code panel.

Environment

• Claude Code in Cursor (VS Code extension)
• macOS
• Skills located at ~/.claude/skills/

Expected behavior

Skills created during a session should be immediately available in the slash-command autocomplete without requiring a session restart. Either:

1. The skill index should hot-reload when new SKILL.md files are detected (file watcher on the skills directory)
2. A built-in command (e.g., /refresh) should force re-scanning of the skills directory
3. The autocomplete index should re-scan on each keystroke or on a short polling interval

Impact

In workflows where skills are created programmatically (e.g., an AI assistant building a new skill as part of a task), the operator cannot immediately invoke the skill. This creates a workflow interruption where the operator must restart the session to use something that was just built.

Workaround

Close and reopen the Claude Code panel in Cursor. The skill appears on the next session start because the runtime re-scans ~/.claude/skills/ during initialization.