Feature request: Improve chat naming when using custom skills

Resolved 💬 3 comments Opened Jan 27, 2026 by aeitauser Closed Jan 30, 2026

Summary

When invoking custom skills (e.g., /newfeature), the VSCode extension names the chat using the internal XML representation <command-message>newfeature</command-message> instead of a human-readable format.

Current Behavior

After creating a custom skill and using it multiple times, the chat history shows entries like:

  • <command-message>newfeature</command-message>
  • <command-message>newfeature</command-message>
  • <command-message>newfeature</command-message>

This makes it impossible to distinguish between different chats when searching or browsing history.

Expected Behavior

The chat should be named using a more descriptive format, such as:

  • newfeature: email-reengagement (skill name + first argument)
  • New Feature: email-reengagement (formatted skill name + argument)
  • Or simply use the first user message content after skill expansion

Environment

  • Claude Code VSCode Extension
  • Windows 11
  • Custom skills defined in .claude/skills/

Suggested Improvement

When a skill is invoked, extract the skill name and arguments to create a readable chat title instead of using the internal command representation.

---
Reported via Claude Code

View original on GitHub ↗

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